Just a thought.
I didn't read through all of your code, but I did read your stack
trace listing with comments.
It appears that you have a path j:\cildata2\... for data, and
another c:\cil data 2\... for your programs. I don't see any
evidence of any double quotes around paths that contain spaces.
It may not be of significance, but depending on the use of those
paths in variables/substitutions/etc., you may get some interesting
errors from the c:\ path that contains spaces.
Do you think there is any chance that you are experiencing a strange
path issue when your error code executes? You would have to
re-compile and rename all your folders to fix it...
Thank you. That post finally arrived!
The path stuff in my post comes from my logging code, which outputs
these locations because I have at times experienced issues due to
loss of connectivity to the file server where the shared data
resides. Those issues seem unrelated to the current problem, because
the error (VFP Error 3, "File is in use.") implies that the code can
access the shared data.
The shared data is in a .dbc database. The path to the shared tables
and .dbc is pulled from persistent local storage at program startup
and then the database is OPENED. After that, VFP can "see" all of the
shared tables without regard to the path by virtue of them being in
the database.
My code treats any path expressions as "name" expressions and
surrounds them with parentheses at all times to make sure spaces
don't cause a problem. I'm not seeing any "not found" messages
related to tables, or any funky errors resulting from truncated path
expressions.
Also, the path containing spaces is CURDIR(), which is where the
program and some local tables reside. The code doesn't have to apply
paths when referencing tables in the same location in which the code
is running. I have recently partially modified the code to define and
persist a local "writeable" location to comply with current MS
standards but in all current production settings, the local tables
are in CURDIR(), which is always the same:
C:\CIL Data 2\
Part of the installation of the software involves assigning users
(typically "restricted" Domain users) "Modify" rights on the
location. This, plus the fact that the software is installed to a
folder in the root, and not under \Program Files\, avoids
"virtualization" issues in Vista and later OSes.
Also, the problem scenario I've been discussing occurs during program
shutdown, not start-up. If there were problems with the path the
program wouldn't even get off the ground.
Thank you for looking at this and any further thoughts are welcome.
Ken Dibble
www.stic-cil.org
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/CF.31.27601.24E8AA55@cdptpa-oedge02
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
