By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,289 Members | 1,793 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,289 IT Pros & Developers. It's quick & easy.

Access 2003 - SQL Server - Records apparently delete but don't

P: n/a
Hi
I am using Access 2003 mdb as a front end to an application which uses
SQL Server 2000 as the backend. The two are connected using ODBC.

On one particular table (the Stock table), I have a simple form which
updates stock. When the user presses the delete key, he gets the usual
warning about not being able to undo this command, and the record
disappears from the screen. However, on some records, when he goes
back into the form, the record has not been deleted and is still
there. It doesn't happen on all records, just some. I've not so far
been able to identify a pattern.

How can this be possible? Are there any issues between Access / Odbc /
SQL which could cause this? Perhaps something like dbSeeChanges which
needs to be used when updating a recordset. However I don't use any
code when the user deletes - perhaps I should. There is no "on delete"
code.

Any help greatly appreciated because I feel like I'm going mad!

Thanks

Colin

Jan 24 '08 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Bobby wrote:
Hi
I am using Access 2003 mdb as a front end to an application which uses
SQL Server 2000 as the backend. The two are connected using ODBC.

On one particular table (the Stock table), I have a simple form which
updates stock. When the user presses the delete key, he gets the usual
warning about not being able to undo this command, and the record
disappears from the screen. However, on some records, when he goes
back into the form, the record has not been deleted and is still
there. It doesn't happen on all records, just some. I've not so far
been able to identify a pattern.

How can this be possible? Are there any issues between Access / Odbc /
SQL which could cause this? Perhaps something like dbSeeChanges which
needs to be used when updating a recordset. However I don't use any
code when the user deletes - perhaps I should. There is no "on delete"
code.

Any help greatly appreciated because I feel like I'm going mad!

Thanks

Colin
Frankly I find your description (at face value) to be difficult to believe.
In my experience edits, insertions, and deletes against an ODBC source
either work exactly as they should OR you get an error.

Is your form based on this table link directly or is it bound to a query?
If a query does the query use JUST the one table or does it join to others?
If the latter perhaps the record that you see "come back" is not coming from
the table that had the deletion applied to it.

If you open the table link datasheet directly and delete a row does that
work? For that matter are there other users and/or applications that
connect to the same ODBC source? Perhaps the record is just being
re-entered via some other mechanism after your app successfully deletes it.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
Jan 24 '08 #2

This discussion thread is closed

Replies have been disabled for this discussion.