>>Did you get the same error and then try the steps I mentioned?

NO, no, that worked fine, in fact I found the same solution you provided from a previous thread that Kevin McNeish responded. That definitely solves the problem, which is weird but it gets solved. Thanks!.

>>>I have two MM applications running now that uses this setup of running the EXE on the local drive against server located data. I created an separate setup (InstallShield) for the workstation so all the correct Runtimes and DLL's are installed on it and that it creates a local folder for the executable and the resource and Classes tables. Also included are the two files - launcher program and it's .ini. Other than those I don't have a need for anything else in the local folder.

I've doing it the same way until version 7, when I started experiencing what I mentioned. My app. keeps asking for the errorlog.dbf, I am able to overcome this issue if I create a copy of it inthe local drive in he same folder where the exe is and as a 'free table'. But I wanted to have the errorlog as a common table for the application.


>>>Another thing - early versions of MM had the errorlog outside the DBC. If this is the case and you're working with a version earlier than 6.1.2 then make sure errorlog.dbf is in the network folder or the folder where the executable is.

I'm working with the latest MM version, 7. To me is clear now what's going on: for some unknown reason the dataenvironment class for errolog is looking for a free table named errorlog under the same path that the exe is running, and not in the database. Would like to know why this happens though...

Thanks for the follow up.