Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
File locations /executable
Message
De
23/06/1997 12:02:24
 
 
À
19/06/1997 19:01:32
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00036780
Message ID:
00037447
Vues:
39
Wow- Good eye!. It was the semi-colon giving me woes all along. I don't know how I looked at this code so many times without catching it. I guess sometimes it just takes somebody else looking at your code to see things. Thanks for your time and help.

>Erik,
>
>If this is a cut/paste of the code, then the semi-colon following "REPORT" in the path line will, as it is written *NOW*, cause the next line to be taken as a comment. Prior to commenting that line I guess it would have given a strange PATH indeed.
>
>good luck
>
>Jim N
>
>>>>>> even though the directory it can't find is the one with the library in
>>>>>it.
>>>>>> If I change the SET PATH TO, however, it looks for the library in the
>>>>>> server directory and says 'library doesn't exist'. How does this work?
>>>>
>>>>Yes, I use relative paths, but I'm not sure why. My program (in compiled form) shouldn't have to look for ANY external files, since all of my libraries are included in the project. My problem lies in the fact that the program does not recognize the names of included libraries and searches for them externally, and fails. Any volunteers to look at a snip or 2 of my code (that is if you didn't see it yesterday when I posted it to Edward)? Thanks
>>>
>>>I checked my current coding structures, and I start calling CreateObject() before a PATH is even set (as a matter of fact, it's the instantiation of an object and execution of a method in it that *sets* my application's path).
>>>
>>>The one thing that stands out in your code is the use of the hard-coded "CD" statement. Why are you doing this?
>>
>>Good question. The reason that it was in there in the first place is that the example I modeled my startup program after had a similar statement. I commented it out for now.
>>
>>I'm not sure why my program needs a PATH statement in the first place, except to tell it where to look for the data. If all of the program's components are included in the app build, why should a PATH statement include anything but the locations of the data? Yet if I exclude the PATH, or set it explicitly to where the data is only, the program can't find the libraries from which toinstantiate my objects. The most maddening thing about this is that the program WORKS on another machine if I set the path to include the location of my libraries (on my drive; inaccessible from the other machine), it just gives an invalid path error from the CD statement. But remove the statement, and it says it can't find the libraries. The current version of the relevant code follows (doesn't work)
>>
>>lcLastSetPath=SET("PATH")
>>*!* CD "c:\atpedb"
>>*!* SET PATH TO ;DATA;INCLUDE;FORMS;GRAPHICS;HELP;LIBS;MENUS;PROGS;REPORTS;
>>lcLastSetClassLib=SET("CLASSLIB")
>>
>>SET CLASSLIB TO myclasses ADDITIVE
>>SET CLASSLIB TO atpedb additive
>>SET CLASSLIB TO appwiz additive
>>lcOnShutdown="ShutDown()"
>>ON SHUTDOWN &lcOnShutdown
>>ON ERROR ErrorHandler(ERROR(),PROGRAM(),LINENO())
>>_shell="DO Cleanup IN progs\atpedb"
>>
>>*!* Instantiate application object.
>>RELEASE goApp
>>PUBLIC goApp
>>goApp=CREATEOBJECT("wzApplication")
>>
>>The first error that this gives is 'can't find myclasses.vcx'
>>
>>And myclasses IS INCLUDED in the project
>>What gives?
Erik Moore
Clientelligence
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform