Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

PDox 8 form error in PDox 10

Status
Not open for further replies.

OmniBoy

Programmer
Jan 31, 2002
2
CA
Hi

I have some forms that work in Paradox 8, but in 10 they will not compile. The affected forms are forms that call another form when pushing a button. The offending code (which works fine in 8) in under the "uses" methode. The code looks like this:

Uses ObjectPAL
"file1.fsl"
"file2.fsl"
"file3.fsl"
endUses

The error generated is:
Error: Version number does not match. Open and save the file.

The sub-forms being called do not call any other forms, and they work fine in Paradox 10

Also, is it worth it to upgrade to 10? I can stay on 8 if 10 doesn't offer anything new beside the more reasonable interface.

OmniBoy
 
That error is usually due to a form being called that was compiled with another version. Since you are calling uncompiled forms (FSLs) I can't image what the problem might be. I don't use USES for calling other forms since I've never found it to be necessary. Try remarking it out and see if the form will compile. I upgraded from 8 to 9 (before 10) because of issues between 8 and NT. I have no plans to go to 10 anytime soon.

Mac
 
OmniBoy,

While Paradox will recompile documents (if necessary) when they're opened, I don't believe the parser does this when checking syntax. As a result, I've found it best to resave all documents (forms, reports, scripts, and libraries) when switching between versions.

Personally, I use a script that scans a directory (and its subdirectories) before opening things in the new version. This also lets me check for common mistakes, such as:

-- Saving forms (or filters) with active ranges or filters.
-- Ensuring that Compiler Warnings are enabled.
-- Making sure that permanent aliases have been defined (though I use project aliases more than permanent ones; fewer headaches).
-- Stylesheet problems (more important than you might realize; details at -- Deploying tables containing test data.

And so on.

If you'd like to see what such a script might look like, take a peek at which outlines the basic process. There's a link to a downloadable sample you can tailor for your own needs.

Hope this helps...

-- Lance
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top