Cannot Update Cursor after moving project from NT3.51 to XP

[mp9]

I'm using VFP5 on a project I've inherited from a long-gone developer.

I've just installed VFP5 on my XP desktop, and all seems to work well. I've copied all the source code from an old NT3.51 box to my PC and it loads up fine in VFP5. I can even build an APP or an EXE as long as I don't check the 'Recompile all files' option. If I do, the build falls over with a message "Cannot update cursor".

I've read all the messages on here that indicate a possible cause of this being read-only project files, but I've been through every file involved in this project and none of them are read-only. It fact, the only interesting things about these files is that they have been copied from the old NT PC to a network share, and then to my XP PC, and that they have the "Archive" (A) file attribute set.

I get the same problem if I try to build an installation kit using the Setup Wizard, except the error message is more detailed - it is then:

Error #111 in checkcompressfiles (0): Cannot update the cursor

This is then followed by:

Alias 'SETUPWIZARD' is not found.

and the Setup Wizard bombs out.

I have to make some changes to my departed colleagues application urgently, so any suggestions or ideas as to what could be causing this would be much appreciated.

Thanks,
mp9

 

[Neil Toulouse]

Check this page on Mike Lewis's web site:

http://www.ml-consult.demon.co.uk/foxst-31.htm

I have found it a very useful routine in the past!

Neil

I like work. It fascinates me. I can sit and look at it for hours...

 

[mp9]

Thanks Neil. Unfortunately, I tried this but it doesn't seem to work in VFP5, unless I am doing something stupid (which is possible).

Any other ideas, anyone? I don't think it's the project (famous last words, I know) becuase if I try to run the Setup Wizard with no project open, I get the error messages shown in my previous post even before I get asked to specify a project.

Any further ideas, anyone?

 

[Neil Toulouse]

Shot in the dark this one! Have you tried deleting all the .FXP files and then recompiling the files via the project?

I like work. It fascinates me. I can sit and look at it for hours...

 

[mp9]

Thanks for your suggestions. What it turned out to be was this.

I needed Administrator priv's on my PC. Corporate policy is for users (even developers in the IT department, like me) not to have admin priv's. The VFP installation was done by an administrator and so I couldn't modify any of the files or write to relevant directories for setup to run.

I'm now an Administrator and all is well... so it wasn't the much touted read-only file attribute but it was my inability to write, if that makes sense!

 

[Neil Toulouse]

Glad you sorted it in the end

I like work. It fascinates me. I can sit and look at it for hours...

 

[dbMark]

Not only that, but XP won't let a non-Administrator write to the root directory of the system drive such as C:\. Security rules. Makes sense, but you can waste a lot of time trying to figure that one out too.