Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

#error - What causes this error?

Status
Not open for further replies.

BrookeSmith

Programmer
Jul 19, 2000
4
US
Once in a while one field in one record shows #error.  This causes jet failure and indicates another user has updated the same record. This is not true. You cannot page up or down past this record. I have to delete the entire record even though only one field has the #error. (The application is a split database with the tables database on a server and each user running a front end to the external data tables database. 64 users use this over a 5 state WAN.) Any ideas??
 
We ran into this many times. That record, has somehow been corrupted. The only solution we could come up with was to highlight the record, print it out, delete it, and re-enter it. Come to find out that there was actually a vidoe card on one of the user's machines that was causing this. It got to where it was happening about every other day.<br><br>I will look for the information about the video card. One particular model of one particular brand can do it. I will let you know when I find it.<br> <p>Jim Lunde<br><a href=mailto:compugeeks@hotmail.com>compugeeks@hotmail.com</a><br><a href= Application Development
 
It's actually not necessary to print the record out, you can highlight it and cut it from the table.&nbsp;&nbsp;Once you cut it, go to the edit menu up top and do a &quot;Paste Append&quot;.&nbsp;&nbsp;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Once the append of the data is complete, you should be able to write over the &quot;#Error&quot; message in the field.&nbsp;&nbsp;Also, what I've noticed is that it seems to occur most often in memo fields.&nbsp;&nbsp;Let me know if this is where it has been occuring for you, thanks. <p>xtreme1<br><a href=mailto:rbio@excite.com>rbio@excite.com</a><br><a href= > </a><br>
 
Oh, and also.&nbsp;&nbsp;The cause of the error is when two people update a record concurrently.&nbsp;&nbsp;One of them, the last to attempt to exit the record, will receive a message:<br><br>&quot;This record has been altered since you have started editing it.&quot;<br><br>They then have a choice of either:<br><br>A) Saving changes<br><br>B) Copying the data to the clipboard<br><br>C) Dropping their changes<br><br>If the users choose to save their changes, an #Error will be found in that record the next time it is visited.&nbsp;&nbsp;If they drop changes, no error will be found.<br>Copying changes to the clipboard does not cause an error either, but in most cases(for me atleast), this is not helpful to the user.&nbsp;&nbsp;He/She will probably not be able to repaste the data into the record anyway.&nbsp;&nbsp;Their best bet in my opinion is to drop their changes, wait a few moments, the re-enter the data.&nbsp;&nbsp;Good luck! =] <p>xtreme1<br><a href=mailto:rbio@excite.com>rbio@excite.com</a><br><a href= > </a><br>
 
I am having this same probloem. It is in a Memo field and may be happening from either the same computer or two computers in the same office. I am never able to reproduce the problem from my machine.

Does this only happens during optimistic locking? What type of locking do you guys use or suggest? My form with this problem has four tabs, each with it's own query, and a list box used to view the records details.

Thaks. Sean.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top