James E. Harvey wrote: > I am using an auto inc field as the pk index tag. > > Today the user could not add a record due to pk uniqueness violated? > > I opened the table and found the "Next Value" set to "4"? There are over > 275 records already in the table. I opened on older backup of the table and > the "Next Value" was okay. > > Does anyone know how the "Next Value" field could be reset to an apparently > random number? > >
Hi Jim (...fellow CPVFUGer)! I use the AutoInc fields and they've continued to work fine for me. If you're using any Views, make sure the AutoInc field is NOT updatable! Perhaps that's it? Also, Pablo's post is good too---is there any chance of someone else opening your tables via VFP or perhaps even something else? You might want to put something in place (like the DBC Events?) to prevent unauthorizing openings of your VFP tables. -- Michael J. Babcock, MCP MB Software Solutions, LLC http://mbsoftwaresolutions.com http://fabmate.com "Work smarter, not harder, with MBSS custom software solutions!" _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
