![]() |
![]() |
|
![]() |
Subject: FAQ:PdoxWin:Incompatible ObjectPAL Version:1999.12.13 Version 1.0 (1999.12.13) edited by Paradox FAQ Team Repost by Mike Irwin: 2001.02.05 Repost by Mike Irwin: 2001.05.25 ==================== 0. Introduction ==================== This FAQ addresses a common problem encountered when using Paradox Reports. Sometimes the runtime system will refuse to load a report, complaining that the underlying table structure is incorrect. This FAQ is appropriate to users of all versions of Paradox for Windows ------------------------------- 0.1 Legal Info and Disclaimers ------------------------------- Paradox is a trademark of Corel. Borland Database Engine (BDE) is a trademark of Inprise. The information provided in this FAQ is provided "as is" and is not warranted in any way. The information provided in this FAQ is not endorsed or authorized by Corel or Inprise in any shape, form, or manner. The editors claim NO responsibility for ANY illegal activity regarding this file, or as a result of someone reading this file. You may distribute this file, as long as the copies are complete, unaltered, and are in electronic form only. ------------- 0.2 Feedback ------------- Please send feedback in a Corel Paradox newsgroup or the news:comp.databases.Paradox newsgroup to any of the FAQ Team mentioned in the "FAQ: FAQ FAQ" document. Please preface the subject of your post with the string "PDXWIN FAQ" to alert Team members to the function of the message. Please specify the FAQ name and section number the comment applies to, if any. ============================== 1. General Problem Information ============================== A delivered *.RDL file has an error sometimes, which asks you to recompile it. The error message is: "Error, The ObjectPAL version used in this report is incompatible with this version of Paradox. You must recompile from the source." =============== 2. Explanations =============== The most common reason for this error is that the table used for the report is not the same structure as it was when the report was last delivered. This can happen if the report is run on another machine where the path names to various tables in the data model of the report are not the same as where the report was delivered. Another reason it can occur is when the report runs off a query and there are calculated fields that reference a field in the query. Again, sometimes the query can change and the expected field is no longer in the position expected. On a very few occasions it has beenseen that some calculated fields just don't allow a report to be delivered. =========== 3. Remedies =========== Most often the only way to cure this problem is indeed to recompile the report (open the .RSL version in Design Mode, take it into View Data Mode to check that it functions correctly, return to Design Mode, and save it. After that you can deliver it again. However, as a part of the cure you should ensure that you are not modifying something that is not incorrect. For example, with a report based on :PRIV:ANSWER.DB, it is quite possible to obtain this error if the query to produce the table fails, leaving a table of that name from some other query. In this case the fault lies not with the report, but with the code ! There is nothing wrong with running a report from the source version. If you are worried about users altering the report without authorisation, keep a note of the date, time, and size attributes of the proper report in a table and compare them to the report every time it is used. Use the FileSystem type's methods to obtain this information. Paradox Community Newsgroups |
![]() Feedback | Paradox Day | Who Uses Paradox | I Use Paradox | Downloads ![]() |
|
![]() The information provided on this Web site is not in any way sponsored or endorsed by Corel Corporation. Paradox is a registered trademark of Corel Corporation. ![]() |
|
![]() Modified: 15 May 2003 Terms of Use / Legal Disclaimer ![]() |
![]() Copyright © 2001- 2003 Paradox Community. All rights reserved. Company and product names are trademarks or registered trademarks of their respective companies. Authors hold the copyrights to their own works. Please contact the author of any article for details. ![]() |
![]() |
|