Link to home
Create AccountLog in
Avatar of fmoore0001
fmoore0001

asked on

Form Instantiaing Error

Guys,

I had a recent computer crash that seems to have wrecked some havoc in my Visual Foxpro 9.2 system.   The first problem was that I could not open sections of Foxpro.  I solved this by reinstalling Visual Foxpro, but the second was far more incidious.  

I found that I would open forms and they were stating that some Class libraries not found.  I always backup, so I restored the entire directory from my backup.  No good.  So that is not a solution.

The error occurs in this fashion.  I open a form (most of the forms are based on a couple of classes), erroring during the load with "Error instantiating class.  Cannot find r:\source code i-servicing\inservicing\g3\class\aco\aco.vcx.

There is a DIRECTORY r:\source code i-servicing\iservicing\g3\aco but ACO.VCX was moved to r:\source code i-servicing\g3\class\aco years ago.  Why the revert?  What is worst is I cannot save the new directory location, even though when I select the correct path for one form it does it for all forms.   But, saving the form does not save the new path.  If I restart Foxpro I have to do the whole dang thing again.

And, when I go to compile the forms I get an error: File r:\source code i-servicing\g3\class\aco\aco.vcx is in use and cannot be recompiled.

What worst, is now I am getting a set of errors in my code after compiling.  A typical example is:

laHolidays[1] = {09/01/01}      
Error in line 676 of frmCLIENT.rawachmicrodeposits (record 77): Ambiguous date/datetime constant. Use the format:
  {^yyyy-mm-dd[,][hh[:mm[:ss]] [a|p]]}

So, anybody got an idea what the heck is going on?

Frank
ASKER CERTIFIED SOLUTION
Avatar of Pavel Celba
Pavel Celba
Flag of Czechia image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
Avatar of fmoore0001
fmoore0001

ASKER

Pcelba,

That is the kicker here.   it does this with my backup as well as my original files.  It makes me think something in Visual Foxpro is messed up.  Yet, I reinstalled 9.2.

give your suggestions a try.

Frank
VFP is just one EXE and two DLLs. I don't think it can be corrupted this specific way.

The reinstallation itself cannot cause any further damage, so I have nothing against it.

More problematic is UAC in Windows 7 and Vista...
PCELBA,

You were right.  The re-install set my Foxpro option settings to SET STRICTDATE TO 1.  But, in the office we had by agreement set to 0 years ago.  Just forgot.  As soon as I set to 0 the compiler worked again.  THANKS!