At 01:39 PM 6/24/2013, Tom Frederick wrote:
I have run into a string of Primary Key auto-numbers that change for no reason I can see. Table 'Goals' is associated with Table 'Objectives'. Objectives has 1020 rows and the most recent row is 1020. This morning, users are getting errors when they add new rows to Objectives. When I use Design Table to look at the PK auto-number value it says 954. Obviously, if a new row gets added an error is thrown. This is not the first time this has happened. What could cause a PK value to change? I rebuild the database regularly. Is there any way I can reset the PK value to 1021 (or whatever I need) while users are still active in a compiled v95 database with latest updates.
Tom, That is a typical symptom of migrating (Unloading/Loading) data from one database to another, without understanding and following the proper method when Autonumbered columns are involved. IF that is the case, I have designed a bullet-proof routine that will help you take care of such issues, when migrating data from one database to another. Let me send you an invite on "join.me" to illustrate the technique, sometime this afternoon. Very Best R:egards, Razzak. www.rbase.com www.facebook.com/rbase -- 30+ years of continuous innovation! 15 Years of R:BASE Technologies, Inc. making R:BASE what it is today! --
