1. Home
  2. Point-Of-Sale Software
  3. Database changes from 1.3 to 2.0 affecting custom reports

Database changes from 1.3 to 2.0 affecting custom reports

I just installed an upgrade from 1.3 to 2.0. The customer has some custom reports that worked fine in 1.3, but don't run anymore in 2.0. I suspect that some of the table or field names are not the same. When we try and run one of the custom reports we get this error: Alter Table VIEWSTOREQTY and Alter Column DAYOFYEAR DATETIME" Then when I hit OK, I get this additional message "(5) Invalid Procedure call or argument." I have a copy of the custom report, but don't know how to identify which table names or fields have changed. Where would I find a list of table and field names in 1.3 and what they are not in 2.0 if they have changed? I can email the report to someone if they would like to see it.

Reply to
L. Pawlak
Loading thread data ...

hi Pawlak, its strange becuase it is minimal change in database level, even few fields are added, what I scan see from your below query is that you added the view or created the view using the query tool, it seems that they are deleted when you upgrade the database. No problem either send one of your report to me so I can repair it for you or you can recreate the view.

If you have backup of old version restore as new database on same or different server, generate the script for only view and then runt he script to new 2.0 version database.

Let me know if you need more help.

"L. Pawlak" wrote:

Reply to
Akber Alwani

Reply to
L. Pawlak

I just tried to run this report last night and here is the exact error message I am getting. "The report data could not be loaded due to the following error (6) overflow

"L. Pawlak" wrote:

Reply to
L. Pawlak

Reply to
L. Pawlak

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.