Is there code in the process to update the date time stamp of the local file after it is copied? When the network file is read only, it may be problematic to get that specific information.
Tracy -----Original Message----- From: Ted Roche Sent: Monday, February 22, 2010 11:03 AM Resurrecting an old thread... So, we've got a VFP program, startapp.exe, circa 1998 by the late lamented Blackstone Inc., which reads a startapp.ini in the same directory, and checks for the existence and timestamps of the main exe. If the EXE isn't in the directory, or the one on the network path specified in the INI file is later, it copies the EXE from the network share to the local drive. It then executes the EXE. Works fine on Win 98, NT, 2000, XP, Server 2008 and Vista. Not working in Win 7, giving us errors. A befuddled error reporting routine reports error #1 on line #0 with the command matching the shortcut to the program, DO startapp.exe with "c:\program files\ucoes\ucoes.ini" Clues appreciated. 1. Program is installed by default to c:\Program Files\Vucoes. I've heard that's problematic. Moved the files to the C:\Vucoes directory instead, and I'm still getting the same error behavior. 2. Current runtime is VFP 7. 3. OS is Win 7 Professional, 32-bit. 4. Machine is ThinkPad W700, Core2Duo 2.8-ish GHz, 4 Gb RAM, lotsa screen real estate. Walking through the code step-by-step in the VFP IDE on our Win7 box, I can read the ini file, and issuing a VFP COPY FILE ... TO ... works fine. "Works fine on my machine" is never something to tell a client, though. We're going to try to instrument some better debugging and testing, but in the mean time, if this clicks with anyone on a problem they've already solved, I'd appreciate any hints. "Without Walls, who needs Gates or Windows?" On Fri, Nov 13, 2009 at 5:57 PM, Ted Roche <[email protected]> wrote: > On Fri, Nov 13, 2009 at 5:16 PM, Charlie Coleman <[email protected]> wrote: >> >> One thing I would advise in general is to not install your >> application under the "\Program Files\" branch. Most places I see now >> are installing things under some other folder (e.g. >> c:\corp_programs\) where they actually have control of assigning access rights, etc. >> > > Mmm, looks like we might need to build a new setup, then. > > >> Also, if you have more than one .exe, make sure none of them have the >> words "setup", "update", "install"... (a couple other words too) - >> I'm not sure about Win 7 but Win Vista would just arbitrarily block >> execution of those (because the "names" sounded like something only >> an "administrator" should run). > > We're using a classic app loader, where "startapp.exe" reads an INI > file, checks to see if the updated files on their network share are of > a later timestamp, copy the newer .exe if necessary, and then launch > it. I'll guess I probably won't be able to do that under "Program > Files" without too much work. > > Thanks for the tips! > > -- > Ted Roche > Ted Roche & Associates, LLC > http://www.tedroche.com > _______________________________________________ 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/001301cab406$5014bbe0$f03e33...@com ** 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.
