I think all exe's start in the windows\system32\ folder when they don't have a "start in" defined. That's why my first few lines of code navigate to the proper location before executing further.
John -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Allen Sent: Thursday, July 26, 2012 9:28 AM To: [email protected] Subject: RE: VFP9 windows 8 That's exactly what it still does even thought the full path is in the target Al -----Original Message----- I remember this happening way back in the 90s. I was trying to do a com app for reindexing SBT tables on the server instead of dragging them across the network. I knew what folder my app was in but sys(5), or what ever that function is to get you your path, always came back with \\Server\Windows\System32\ initially. [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** 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.
