Problem with HQ Export Database

RMS/HQ 2.0 SP1 SQL Server Standard 2005 SP2 WinXP SP2

I'm trying to create a store database for a new store. I've got the Master Store and the Template Store DBs created and populated from an existing store DB. The HQ database was created using the blank HQ database backup and I imported data from the Master Store DB. I created 2 stores in the HQ database--one for the existing store and one for a new store we are getting ready to open. All this appears to have worked OK.

I'm now at the point where I use HQ Admin | Database | Export to create a store database for the new store. The process appears to work up until the app tries to populate the new database with data from the HQ Template Store DB (I assume). I checked the new database immediately after it was created and there were only system tables defined. After copying from the template store database, all the RMS tables were defined, but empty. So far, so good (again, I assume). Now, when the process is exporting the data, it gets as far as the Item table and I get an error:

Export Database Wizard: An error was encountered while exporting data. Your Store Operations database is not complete and may not work correctly. Error 0:

That is sure a lot of help (sigh!). The Item table is empty in the new store database, some of the previous tables (Cashier, Category, Department) have exported data, none of the tables following the Item table have data.

I've done all this twice with the same results. Is there a log somewhere that can tell me where to start looking for the exact problem? Has anyone else encountered something like this before and can provide a solution/workaround. Any help will be greatly appreciated as I'm dead in the water right now.

thanks, randy

Reply to
Randy B.
Loading thread data ...

I did a little more testing and think I found what went wrong: We have 2 non-RMS tables in our store databases that are used to manage Special Sales information (above what RMS sales functionality provides) used by an add-in. When I removed those tables from the HQ Master and Template store databases, the export completed successfully. My conclusion is the Master and Template store databases need to be "vanilla" RMS databases.

I can workaround this by adding back the non-RMS tables to the store database after it is exported. Of course, the real solution will be to move those tables to their own database and do cross-database joins, which will have to be done at a later time.

thanks, randy

Reply to
Randy B.

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.