Can't Update Store Register Information

I was going to add a second receipt printer to one of my register's, but when I hit the OK button, I get an error: "Insufficient key column information for updating or refreshing".

I am running RMS 1.2.0189 with 4 stores and HQ. The server is running windows server 2000 with SP4 and had SQL 2000 with SP3a. I decided to update SQL to SP4 last night, but that didn't solve my problem.

To further test things, I attempted to add a new register into the system and it gave me the following error: "Cannot insert the value NULL into column 'StoreID', table "LitchfieldStore.dbo.Register'; column does not allow nulls. INSERT fails."

About two weeks ago, I did do a database check and reindex on this particular store. Would this have anything to do with it? One of the other

3 stores databases is setup on the same SQL server and I am able to update/change registers in that store without any of these problems. I haven't done a DB check or reindex on this other store.

What could've happened here and how can I get this working?

Thanks, Michael

Reply to
Michael Behm
Loading thread data ...

Tell me few things,

  1. Have you upgrade the RMS ever.
  2. Have you play on back-end in your database
  3. If you are configuring the second receipt printer have you configure it on register property as second printer also.
  4. Do you know how to use SQL Profile if so it will be very easy to find what is the problem.

Regards Akber

Reply to
Akber Alwani

I am running RMS 1.2.0189 with 4 stores and HQ. The server is running windows server 2000 with SP4 and had SQL 2000 with SP3a. I decided to update SQL to SP4 last night, but that didn't solve my problem.

To further test things, I attempted to add a new register into the system and it gave me the following error: "Cannot insert the value NULL into column 'StoreID', table "LitchfieldStore.dbo.Register'; column does not allow nulls. INSERT fails."

About two weeks ago, I did do a database check and reindex on this particular store. Would this have anything to do with it? One of the other 3 stores databases is setup on the same SQL server and I am able to update/change registers in that store without any of these problems. I haven't done a DB check or reindex on this other store.

What could've happened here and how can I get this working?

Thanks, Michael -- First District Association

Reply to
CptSoft
  1. Have you upgrade the RMS ever.

The last upgrade was done on 9-25-2005. I installed the latest pack and hotfix for the RMS system.

  1. Have you play on back-end in your database

I have done a few inserts into the customer table (at HQ level) to add data to the customtext fields. I also have done some inserts in the register table (at the store level) since having this problem. I needed to change the receipt printer 1 name.

  1. If you are configuring the second receipt printer have you configure it on register property as second printer also.

I'm not sure what you are asking here exactly. I added the second printer to windows. I then attempted to add the printer into the receiptprinter2 tab (going into store ops manager -> database -> Registers -> register list). Is there somewhere else I need to setup a printer?

  1. Do you know how to use SQL Profile if so it will be very easy to find what is the problem.

I haven't really worked with Profiler. I do have it installed, but haven't worked with it. I would be comfortable using it with a little guidance.

Thanks for your input thus far.

Mike

Reply to
Michael Behm

Jeff,

I hear you. I'm not sure where to start. This problem could have existed for a year possibly because we haven't had to make any changes to the registers in that time. Or, it could have something to do with the re-indexing. I'm fairly certain it's not becuase of the sql server itself because of the other store that has it's database hosted on the same machine.

I'm hoping that the upgrade to 2.0 will fix things.

In regards to a 2nd receipt printer, is there anything I need to invoke to get that to work? Using the update/insert commands, I've made the changes to the 2nd receipt printer, but it is still printing all copies to receipt printer 1.

Thoughts?

Thanks, Michael

Reply to
Michael Behm

HI I think I can tell u what is the problem. Check the Register table and make sure there won't be any field added with GUID data type. and if possble send me the Register table data structure we can quickly find this.

Reply to
Akber Alwani

Akber,

I didn't see anything in the store's Register table that would indicate it requiring GUID data type. Where would you like me to send you the table structure?

Thanks, Michael

Reply to
Michael Behm

After looking at the table properties and comparing the "bad" store to the "good" store table, I noticed that there is no Primary key set for the "bad" store anymore. Also, all the default values are blank instead of having an entry like the "good" store.

Any idea what could have caused this? Will the fix be as simple as setting up the primary key again?

Thanks, Mike

Reply to
Michael Behm

First run the query below: SELECT * FROM TransactionEntry WHERE [ID] IN (SELECT [ID] FROM TransactionEntry GROUP BY ID HAVING COUNT(*) > 1)

and Make sure the above query not return any row, yes then go ahead and make the ID as your primiary key.

"Michael Behm" wrote:

have to contact Support.

they're gonna do for you.

newsgroup reader to

Reply to
Akber Alwani

Thank you for your input. Just wanted to give you a follow-up that things are working smoothly now.

Michael

Reply to
Michael Behm

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.