J
Justin A.
I found this article "ACC2000: Access 2000 Unexpectedly
Quits When You Run Code to Open an Object" on msdn. It
explains exactly the problem I am having, except this
problem only happens on occasion when I *close* a form.
I have tried the resolution, but to no avail. I started
this database in 2000, but switched over to 2003 just for
a few code changes and have been working in 2000 ever
since.
It only happens when i run my code to send up data
through stored procedures to a UDB table, then try to
delete that record from my local tables.
When i am just tooling around in the database it's not a
problem. When I call data from UDB its not a problem.
When I send data to UDB through stored proc's it usually
isnt a problem. I notice it the most when I am deleting
records from the local tables just using the runSQL
command and giving it a delete call for a record after
they have been sent up.
Does this sound familiar to anyone? I have been going
round and round with this.
Quits When You Run Code to Open an Object" on msdn. It
explains exactly the problem I am having, except this
problem only happens on occasion when I *close* a form.
I have tried the resolution, but to no avail. I started
this database in 2000, but switched over to 2003 just for
a few code changes and have been working in 2000 ever
since.
It only happens when i run my code to send up data
through stored procedures to a UDB table, then try to
delete that record from my local tables.
When i am just tooling around in the database it's not a
problem. When I call data from UDB its not a problem.
When I send data to UDB through stored proc's it usually
isnt a problem. I notice it the most when I am deleting
records from the local tables just using the runSQL
command and giving it a delete call for a record after
they have been sent up.
Does this sound familiar to anyone? I have been going
round and round with this.