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 Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Help!!! Error Message Paradox 4.5 1
- Thread starter steveman
- Start date
-
1
- #2
Steveman,
This is an error generated by a problem with ObjectPaL code being run by your printing process. Look at the code underlying the operator's printing process; something is no longer working.
Sorry I can't be more specific, but the error itself is not enough information to determine the true cause of the problem. You'll need to dig into things a bit more to unearth the real culprit.
-- Lance
This is an error generated by a problem with ObjectPaL code being run by your printing process. Look at the code underlying the operator's printing process; something is no longer working.
Sorry I can't be more specific, but the error itself is not enough information to determine the true cause of the problem. You'll need to dig into things a bit more to unearth the real culprit.
-- Lance
- Thread starter
- #3
Lance,
Do you think the problem could be that the program was originally written for a 16 bit OS and now it is on a 32 bit OS? It worked in windows 3.11 with a 16 bit novel client but will not work in Win 95, Win 98 or Novel 32 bit client for Win 3.11. In what file is the code you want me to look at?
Do you think the problem could be that the program was originally written for a 16 bit OS and now it is on a 32 bit OS? It worked in windows 3.11 with a 16 bit novel client but will not work in Win 95, Win 98 or Novel 32 bit client for Win 3.11. In what file is the code you want me to look at?
Steveman,
Yes, the problem could be a 16-32 bit issue, especially if the underlying system prototypes API calls or functions from other DLL's, such as a third-party.
I can't really tell you which file to look at, having no idea of the system itself. Try to determine which form triggers the error and then see if you can open it's .FSL file in a Design window. (There's an option on the File | Open | Form dialog.)
Before you get carried away, go into Developer Properties and make certain that the Advanced button is selected for ObjectPAL. This will display all the available methods that could contain code.
Once you get the form opened in a Design window, press Ctrl+Space to display the Object Inspector and then open an editor window for one of the available methods. It doesn't matter if there's actually code in there or not; we're trying to add a wee bit of information to what you've currently got.
Once you get an editor window, look for a menu command called Compile with Debug. See if it's checked. If not, choose it and then save your form.
That done, press F8 to run the form and then trigger the process that's currently displaying an error. This should provide additional information about the method and line that the error is occuring on.
Also, when the error dialog appears, take a moment to see if the >> button is enabled; if so, that means there's more specific information available. Click it, write everything down, and then post it.
We should be able to make some suggestions from there.
Hope this helps...
-- Lance
Yes, the problem could be a 16-32 bit issue, especially if the underlying system prototypes API calls or functions from other DLL's, such as a third-party.
I can't really tell you which file to look at, having no idea of the system itself. Try to determine which form triggers the error and then see if you can open it's .FSL file in a Design window. (There's an option on the File | Open | Form dialog.)
Before you get carried away, go into Developer Properties and make certain that the Advanced button is selected for ObjectPAL. This will display all the available methods that could contain code.
Once you get the form opened in a Design window, press Ctrl+Space to display the Object Inspector and then open an editor window for one of the available methods. It doesn't matter if there's actually code in there or not; we're trying to add a wee bit of information to what you've currently got.
Once you get an editor window, look for a menu command called Compile with Debug. See if it's checked. If not, choose it and then save your form.
That done, press F8 to run the form and then trigger the process that's currently displaying an error. This should provide additional information about the method and line that the error is occuring on.
Also, when the error dialog appears, take a moment to see if the >> button is enabled; if so, that means there's more specific information available. Click it, write everything down, and then post it.
We should be able to make some suggestions from there.
Hope this helps...
-- Lance
- Thread starter
- #5
- Status
Similar threads
- Locked
- Helpful tip
- Locked
- Question