Mike Yearwood
Toronto, Ontario, Canada
General information
Category:
Coding, syntax & commands
Environment versions
Network:
Windows Server 2012
>>>>>I just received an error at a client which seems to be related to a network issue. They are starting the executable on a network folder, and once in a while they get an error reading c:\users\cis\appdata\local\temp\kkgmain.fxp.
>>>>>
>>>>>kkgmain.prg is the main application procedure, and the temp folder is my own temp location (where I compiled the executable), so that folder does not exist at the client. It seems that the compiled executable stores path information and therefore comes with this error message. But my guess is that this has to do with a network disconnection and the program cannot find the resources during execution.
>>>>>
>>>>>Can somebody verify this problem and knows a workaround?
>>>>
>>>>Visual MaxFrame has a routine to remove the pathing throughout the app.
>>>
>>>That seems to make sense, because it looks somewhat strange for a client to see your path. They would assume you would have hardcoded a path reference, which looks very amateuristic.
>>>
>>>The strange thing about this path is that is references a file on temp, which for sure I have not referenced anywhere in the project manager.
>>
>>I really don't believe that the path that is shown in error messages like this means anything in reality. I've seen it many, many times before in my errorhandler message. I think this is just how VFP works.
>>
>>And if MaxFrame removes it with a utilty then fine, but I wouldn't worry about it.
>>
>>But if your app is not working then I believe the problem is elsewhere.
>
>
>Yes, the real issue is related to what Erik said, a network disconnection during idle time.
>
>I forwarded the info to the client and let's see if it gets resolved. Unfortunately the executable is being opened on the network share, otherwise I could deal with this using error handling and automatically restoring the database connection after restoring the network.
Change to using UNC naming instead of mapped drives. That has worked wonders for me.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only