Recent content by rgbean

Sorry it took a while to get back to this, but after copying all the pieces over top of their counterparts in all the appropriate directories, everything seems to work just fine! Thanks for everyone's thoughts on this. Rick

Thanks John for the confirmation (although I never got any messages!). I had no problems with 8.0 and 9.0 either - just 6.0 SP5! Rick

Hi Dave, Yup I tried that. In fact I tried running them in XP SP2 compatibility mode too, but still no errors and no success. Since SP5 has the all the files expanded (at least for VFP), I'm considering just copying them over thier base counterparts, and hope that there aren't any critical...

Because I have to occasional support a VFP 6.0 SP5 app, I thought I'd try installing this on my new Vista machine at home. While the VFP 6.0 install went fine, the SP5 update fails because it requires MDAC 2.5 (or higher). While I get no error on the install of 2.5 MDAC (or 2.6), apparently what...

Here is a bit more formalized response: http://fox.wikis.com/wc.dll?Wiki~IdentifyFoxProVersionFromEXE~VFP Rick

If you know you are only running in XP / Vista, you can get additional information with winmgmts. (Some of this info is shown below.) strComputer = "." objWMIService = GetObject("winmgmts:" ; + "{impersonationLevel=impersonate}!\\" + strComputer + "\root\cimv2") colOSes =...

Have you tried using the Compatibility mode on the shortcut? While I haven't tried it yet, I've read some good things about DOSBox - http://dosbox.sourceforge.net/news.php?show_news=1. Rick

You also might get this error if the label file(s) have become corrupted. Try opening the .LBX file. First try it with USE mylabel.LBX Then try Modify Label mylabel.LBX Rick

Here's a routine I wrote a few years back (it could be rewritten using the VFP bit manipulation functions, but unless you're doing a lot of them, this is probably good enough). If you want the bit layout, I've included that at the end. (Feel free to beatify it - most of the layout spacing was...

The runtime files for FPW 2.6a are: FOXW2600.ESL FOXRUN.PIF (if you run any DOS commands in the application) FOXTOOLS.FLL (if you use any of these library functions) FPATH.FLL (if you use any of these library functions) RESERVED.FLL (if you use any of these library functions) and any custom .FLL...

BlackDice, Because VFP keeps as much stuff in memory as it can, it's always a good idea to CLEAR RESOURCES after making these kinds of changes. See the Help file topic for CLEAR for more detail. Rick

savita, Another way to do this is to create an active user table with five records in it. Then when a user logs on, try to LOCK each record until you find one. Then when they exit the application release the lock - if they have connection problems or a system crash the file server will...

I seem to remember that SP3 fixed this for NT/2000. I don't believe SP3 is still available, but the more stable SP5 is at http://msdn.microsoft.com/vstudio/downloads/updates/sp/vs6/sp5/dnldoverview.aspx. Rick

Kate, Does the user running the app have restricted access to the network at night? Have you tried running it at night in the command window? Rick

Steve, Is this form "Modal"? Does it run correctly from inside the VFP IDE? (i.e. DO myapp.exe )We've got VFP executables as large as 35 MB, so no 3 MB is not a real problem. Rick