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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Version Difference

Status
Not open for further replies.

Langley

Programmer
Jan 23, 2002
592
US
I just had an old Paradox 7 application dropped on my desk. The person who designed it is in never-never land so they brought it to my boss, who just so happens to have a Paradox programmer on staff (me).

My problem is that they do not want anything done to it other than to make it work again (they upgraded to Paradox 11 after their hard drive died and Pdox7 Runtime went bye-bye). I assmued that the reasonable thing to do was recompile the source code (since everything pointed to FDLs) and all would be peachy. However, When I do this I get the dreaded ambiguious 'Internal Error' message in the status bar.

I have a reasonably easy (< a days work) workaround, but I thought I'd ask in case there was something simple I was overlooking.

I know I could re-install Pdox7 Runtime, but they want to use the Version 11 they bought.

Anyone have a clue why these forms will not simply compile?


Mac :)

&quot;There are only 10 kinds of people in this world... those who understand binary and those who don't&quot;

langley_mckelvy@cd4.co.harris.tx.us
 
Langley. Try running the forms uncompiled. I'm using both Paradox 7.0 and Paradox 10.0 here. I can write scripts, forms, and reports in seven and all will work peachy keen in ten. As soon as I complile in ten I'm no longer able to access them (especially forms) in seven.

To date the only problem we've had with ten is missing graphics and the occassional disappearing button on system (not embedded form) buttons.
 
Yeah, using the FSLs was my workaround ;) - it's okay since they own the source code, but I thought there might be some explaination.

You see, I can't even compile the source code in version 11 without the error message being generated. There is nothing wrong with the code I can see (it's extremely simple and most of it was done with 'wizards'), it just refuses to compile.

Mac :)

&quot;There are only 10 kinds of people in this world... those who understand binary and those who don't&quot;

langley_mckelvy@cd4.co.harris.tx.us
 
Mac,

First, you'll need to resave all documents (forms, reports, scripts, and libraries) in the new version. I would do that before trying to redeliver any of the documents. (See for a download with a sample script that may help.)

Next, verify all stylesheet information for the forms and reports--even if you doubt that stylesheets were used. Ever since Paradox 5.0, stylesheet information has been recorded in forms and reports. If the stylesheet used to last save the form was located on a drive that's not available to the user running the document, you will see lots of strange errors. (See for an overview.)

I'd also make certain that all tables and indexes are not corrupted. This means you'll need to verify each table. Fortunately, Paradox 11 contains an ObjectPal method that does that, so you can use a script to automate the process.)

I'd also make certain that all filters and ranges are cleared from all documents before delivering.

Finally, see if the datamodels use saved SQL or QBE files; if so, try to rework those portions of the application so they don't need queries to be run before opening the document.

Hope this helps...

-- Lance
 
Thanks Lance, good advice as always!

Mac :)

&quot;There are only 10 kinds of people in this world... those who understand binary and those who don't&quot;

langley_mckelvy@cd4.co.harris.tx.us
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top