Hi Jason,

I moved everything to the F: drive and the mappings all point to the right drive (f:).

I also made sure that the references both in the .ini file and the metadbc table point to f:\program files\ytimeclock\data\yTimeClock.dbc.

The system seems to be working fine now.

I will contact Kevin directly to write a short document about detailed requirements for databases located in directories other than the _applicationPath\data directory, especially when the name of the database is NOT the same as the name of the application, as I'm really not sure about how the .ini/registry and metadbc table relate to one-another.

In addition to that I have had the app complain once about not being able to find the errorlog.dbf table.

Thanks to you and Paul for all your help!

Alex


>Alex, looking at this thread I just noticed something. Note the bold text...
>
>"The database is in a remote drive (G:). This is established in the ini file I'm using and also in the metadbc.dbf table."
>
>
>>YTIMECLOCK=f:\program files\ytimeclock\data\
>>
>>In metadbc.dbf the database address is stated as:
>>f:\program files\ytimeclock\data\ytimeclock.dbc
>
>Did you move your files from the G drive to the F drive?
>
>Another consideration is to use UNC paths, instead of mapped letters. That has worked for us since we have no control over what individual work stations have for drive mapping.
>
>Hope that finally helps!
>---J