Solved: Strange Table Performance/Response
MS Access 2010. I have a VERY simple table, no look ups or whatever. Primary Index is an integer, increment field. There are no other indexes in the table. I had not had to use it for a time, today when an attempt to enter a new record via form directly on the table, the Primary Index gets set to an Index value already contained in the table. Of course the result is the inability to save the record. I have never seen this before, I cannot understand what would have caused this response, especially in Table View, with no form events or other to cause something to be amiss. Is there away out of this dilemma, I REALLY need this table?
MS Access 2010. I have a VERY simple table, no look ups or whatever. Primary Index is an integer, increment field. There are no other indexes in the table. I had not had to use it for a time, today when an attempt to enter a new record via form directly on the table, the Primary Index gets set to an Index value already contained in the table. Of course the result is the inability to save the record. I have never seen this before, I cannot understand what would have caused this response, especially in Table View, with no form events or other to cause something to be amiss. Is there away out of this dilemma, I REALLY need this table?
Last edited: