If the databasename has a underscore, the error occurs randomly on some of the used tables. If the databasename doesn't have a underscore all works fine. (We use the german version of crystal, I'm not sure, if this is the exact english translation) We are not absolutely sure, if databasenames without underscore are never affected from this problem.ġ.) Open a existing (working) Crystal-reportģ.) Error "Could'n find table XY_Z in database. Even in the newest 3.51.19 (and 3.51.20) this problem occurs. If you have to refresh/verify a report definition in Crystal Reports 10 (Build, SP6) you get "randomly" errors for databases with underscore in its name.īefore using newer versions then "ODBC 3.51.12" everything worked fine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |