Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Alias 'ERRORLOG' is not found.
Message
De
10/07/2002 17:06:07
Gil Munk
The Scarborough Group, Inc.
Baltimore, Maryland, États-Unis
 
 
À
02/07/2002 12:11:19
Information générale
Forum:
Visual FoxPro
Catégorie:
The Mere Mortals Framework
Divers
Thread ID:
00673505
Message ID:
00677260
Vues:
35
>As for the dataenviroment, I did so, but still unsuccesful, in case I get same error again will try the exact steps you pointed out and will let you know.

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


>As for the installation, thank you anyway, but I was talking about what MM needs to be set in order to work in a local drive against data on a network, not what VFP needs to, obviously I wasn't clear enough.

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.


>The "errorlog.dbf" table not being found problem , same that you had, started after I switched the Local Database path from my local drive to a network folder and I removed the data folder from my local drive.
>As soon as I reload the application it asks me for the errorlog.dbf, apparently it is not looking for it down the local path established at metadata.dbf or the registry key, and i suspect it is still looking for it at the local drive.
>Since the error gives you the chance to locate "errorlog.dbf" , I do so from the network, and after this the application is reading the data correctly.
>But this is going on everytime I load the application and of course is an unwanted feature ;) at this point.

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.



>So question would be, is there any other MM file other than the EXE, classes.* , msgsvc.* to be set at the local c: drive ? In other words, do you simply put these files I mentioned (add images if you have them) in your c:\appfolder and run it for the first time to get the message where you write what are the local and remote databases ? I'd like to hear yours and others experience on this.TIA.

see above.
Gil Munk


"If a nation expects to be ignorant and free, it expects what never was and never will be." - Thomas Jefferson
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform