![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, since some time i struggle with errror 3167 in an ac2003 form based on multiple tables. In Ac2000 , I haven't any troubles with this form. Probably , it has nothing to do with it, but you never know. When the error occured , i cannot tell exatcly. In this form i have to fill some textfields with a commandbottum. To put the data i have to navigate in the records en go back. I've tried this with a recordsset and rewrite it without a recordset and use this rule "DoCmd.GoToRecord , , acNext/acprevious " depends if i have to go forwards or backwords. When the error occurs, it's hard to tell. sometimes when i leave the form , i get a message " record is deleted", otherwise i get it after run the code. The weird is , i've latest tried the code for more than 100 times ... without an error. Therefore i think it's nothing wrong in my code. I also cannot place a stoppoint in the code , because i am not certain i get an error if the error occured , we cannot open longer the form automaticly. I've manually have to open the db/table and removed the record indicated by "#####". Afterwards , i have to reinstall my primary key. It's apperently a frekwently error , but no specific solution for it. I copied once all the data in a new table and Database , but the error stills occurs; I do not use memofields because i'am afraid of corruption. What can i do to prevent this or i otherwise haw can i handle this error in mine errorhandling. I think it will not help if i when the error occurs, i do an "me.undo" regards Pol |
#3
| |||
| |||
|
|
It's a good idea to "help people to help you" by including the description of an error along with the error number. Few, if any, who answer questions here are doing it to prove how well they can memorize the correspondence between error numbers and the actual error, and, few have a lot of _extra_ time and energy to put into answering questions for free. I agree. A description and error code together help. |
#4
| |||
| |||
|
|
Access Developer wrote: It's a good idea to "help people to help you" by including the description of an error along with the error number. Few, if any, who answer questions here are doing it to prove how well they can memorize the correspondence between error numbers and the actual error, and, few have a lot of _extra_ time and energy to put into answering questions for free. I agree. A description and error code together help. I entered Access 3167 in google and got this link. http://dbaspot.com/forums/ms-access/...-record-delete d.html |
![]() |
| Thread Tools | |
| Display Modes | |
| |