M
Max Moor
Hi All,
I have a form that makes Access throw an error and close itself
(i.e., Access has encountered a problem, and must close). It happens if I
switch the AllowAdditions property of the form to No, and then try to save
it. If I reopen the DB after the error, the form opens, but I get the
error again when I close it.
I was doing this to stop the single form from scrolling to the new
record, but will take care of this another way. I'm still concerned about
this happening though, and would like to know the underlying cause. (It
seems like the kind of thing that used to happen to me when I'd code a bad
pointer in C)
Does anyone have any tips about this: where I might read up on this
sort of thing, or how I might troubleshoot it?
- Max
I have a form that makes Access throw an error and close itself
(i.e., Access has encountered a problem, and must close). It happens if I
switch the AllowAdditions property of the form to No, and then try to save
it. If I reopen the DB after the error, the form opens, but I get the
error again when I close it.
I was doing this to stop the single form from scrolling to the new
record, but will take care of this another way. I'm still concerned about
this happening though, and would like to know the underlying cause. (It
seems like the kind of thing that used to happen to me when I'd code a bad
pointer in C)
Does anyone have any tips about this: where I might read up on this
sort of thing, or how I might troubleshoot it?
- Max