Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Disappearing Data... Help Please!
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Divers
Thread ID:
01307229
Message ID:
01307459
Vues:
4
>Well I took out the USE TABLE AGAIN ALIAS stuff and that seems to have cured the "quirk". I still find it extremely odd that this behavior was limited to the compiled .exe in VFP9. I compiled the same thing in VFP8 and no problem so my thinking goes, there has to be a bug in VFP9. I've spent the last 4 hours building a little project to try and recreate the bug to no avail. If I can't recreate it then I can't prevent myself from doing something similar in the future. I still say there is something weird going on in VFP9 when using the same table multiple times with AGAIN ALIAS. Nothing would make me happier than to find the bug in my code, rather than a quirk in VFP9, however the fact that compiling the EXACT same code in VFP8 makes the quirk go away leads me to believe that it has got to be something in 9.
>
>I HATE these types of "quirks". I feel like I'm looking over my shoulder afraid of the unseen bogeyman.

Yeah, I hear ya on that. A few more questions (and SWAGS):

- did you try running with AV disabled?
- which SP of VFP9? SP0, SP1 or SP2? Hopefully you haven't tried to install SP2 over SP1, this is known to cause problems. To install SP2 apparently you have to completely uninstall VFP9, then reinstall VFP9 SP0 (i.e. no service pack, the original RTM), then install SP2 on that (bypassing SP1)
- have you done an .EXE rebuild with the RECOMPILE ALL option? I'd hate to think you were running with some components' object code still compiled in VFP8
- do the dev and production environments use different FOXUSER files? If so you could try renaming or deleting the production one
- there is a VFPClean.app that may be worth running
- in a couple of cases I've encountered corruption in class libraries that could only be fixed by creating new classlibs and copying individual classes from the old to the new. However, these problems manifested themselves in both dev and production
- I don't know if a corrupted project file could cause anything like this. It's easy to create a new one, though, if you'd like to try it out
Regards. Al

"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov

Neither a despot, nor a doormat, be

Every app wants to be a database app when it grows up
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform