I have setup a configuration file on our network (G: Drive) so that all
users can access it.

I have added 3 databases as below:

Config Path = G:\

   Name      Path

1)   Company A   G:\Data\CompanyA
2)   Company B   G:\Data\CompanyB
3)   Test      C:\Test

This all works fine and I can access all 3 databases.

However sometimes I might not be connected to the network so I cannot
access the configuration file, but I still want to have access to my
local database Test.

How do I do This?

I get an error telling me that the configuration file cannot be found.

I cannot put the configuration file locally as the locking will not work
on the network databases, and I cannot find any way to have more than 1
configuration file.

I am sure that I am missing something fundemental here - probally still
thinking in DBISAM mode. I am a bit late switching because I was waiting
for the ODBC Driver.


Chris Holland

Chris


Why can't you have a local configuration file just pointing at test? If you can't connect to the network they can't connect to you so it doesn't matter that your using another configuration file will prevent their access.

Roy Lambert

Then what happens when I am connected to the network.

From what I understand the record locking wont work correctly.

I think I need 2 configuration files, one for when I am connected and
one for when I am not.(and an easy way to switch between them)

Chris Holland


Roy Lambert wrote:
> Chris
>
>
> Why can't you have a local configuration file just pointing at test? If you can't connect to the network they can't connect to you so it doesn't matter that your using another configuration file will prevent their access.
>
> Roy Lambert
>

Chris


Sorry. I should have been clearer in my post. Two configuration files are exactly what you need: 1 on the network and 1 local for yourself.

When you talk of an easy way to switch between them do you mean in the app or in EDBMan?

Roy Lambert

Both

Roy Lambert wrote:
> Chris
>
>
> Sorry. I should have been clearer in my post. Two configuration files are exactly what you need: 1 on the network and 1 local for yourself.
>
> When you talk of an easy way to switch between them do you mean in the app or in EDBMan?
>
> Roy Lambert
>

Chris


App is a bit more difficult. For EDBMan when you start it up - click on Edit Options and change the config path name. For the app it depends how you set the config path. I personally would use a text file and allow the user to choose as part of the login/company selection. Deactivate the engine and alter the config path if appropriate. You could also just try to open a table, if it bombs fall back to the C:\whatever config path.

Roy Lambert

Thanks for that Roy.

I am using the ODBC driver and the ConfigPath is written to the registry
as part os the installation setup.

Maybe what is needed is an extra option in the Connection String like
"Config=xxxx"  (Tim, how about it?) This would overwrite the default
path if used.

Also a start up switch on the EDBManager like "-c D:\LocalConfig.cfg"
which sets the configuration path so I could just set up 2 shortcuts on
my desktop would be nice.

Chris Holland


Roy Lambert wrote:
> Chris
>
>
> App is a bit more difficult. For EDBMan when you start it up - click on Edit Options and change the config path name. For the app it depends how you set the config path. I personally would use a text file and allow the user to choose as part of the login/company selection. Deactivate the engine and alter the config path if appropriate. You could also just try to open a table, if it bombs fall back to the C:\whatever config path.
>
> Roy Lambert
>

Chris,

<< Maybe what is needed is an extra option in the Connection String like
"Config=xxxx"  (Tim, how about it?) This would overwrite the default path if
used. >>

You can't.  The ODBC driver could be in use already with the engine
internally active on another connection.  The bottom line is that the
configuration path is not a per-connection setting, it is an engine-wide
setting.

<< Also a start up switch on the EDBManager like "-c D:\LocalConfig.cfg"
which sets the configuration path so I could just set up 2 shortcuts on my
desktop would be nice. >>

See this thread:

http://www.elevatesoft.com/scripts/newsgrp.dll?action=openmsg&group=16&msg=2326&page=1

Roy is working on me for a combo-box.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

So how do I use the ODBC driver to access the data on the server and the
local data at the same time as in the senario above.

I use the ODBC driver to run our customer database with the data on the
server and also to access my test data on my local driver.

Chris Holland


Tim Young [Elevate Software] wrote:
> Chris,
>
> << Maybe what is needed is an extra option in the Connection String like
> "Config=xxxx"  (Tim, how about it?) This would overwrite the default path if
> used. >>
>
> You can't.  The ODBC driver could be in use already with the engine
> internally active on another connection.  The bottom line is that the
> configuration path is not a per-connection setting, it is an engine-wide
> setting.
>
> << Also a start up switch on the EDBManager like "-c D:\LocalConfig.cfg"
> which sets the configuration path so I could just set up 2 shortcuts on my
> desktop would be nice. >>
>
> See this thread:
>
> http://www.elevatesoft.com/scripts/newsgrp.dll?action=openmsg&group=16&msg=2326&page=1
>
> Roy is working on me for a combo-box.
>

Chris


You said that the config path is currently picked up from the (yech spit) Registry. You must somehow read it from there and pass it to the engine BEFORE the engine is active so

1. read the network path from the registry
2. test for the existence of the config file
3. if it doesn't exist read the local path from somewhere
4. give the engine the appropriate path.

Roy Lambert