Deleted record reappearing!!!!

[sphynx]

Hi i have a problem with magically reappearing records!!

Basically I have an access database that information is feed to via two manufacturing units using a JSP based web page.

All the information goes into a table and results are calculated in a query.

All data is verified on a daily basis and incorrect records deleted from the query where necessary. This method has been working fine for 6 month but all of a sudden deleting records in the query causing them to reappear when next opened!

The only way round this currently is to delete the entry from the table, this however is not accessible from the user front end and i am reluctent to start redesigning.

Any advice would be greatly appreciated

Thanks

 

[georgedwilkinson]

Hi i have a problem with magically reappearing records!!

Basically I have an access database that information is feed to via two manufacturing units using a JSP based web page.

All the information goes into a table and results are calculated in a query.

All data is verified on a daily basis and incorrect records deleted from the query where necessary. This method has been working fine for 6 month but all of a sudden deleting records in the query causing them to reappear when next opened!

The only way round this currently is to delete the entry from the table, this however is not accessible from the user front end and i am reluctent to start redesigning.

Any advice would be greatly appreciated

So many things could be wrong here and you haven't given us much to go by.

How are records deleted in the query? Through a jsp page? Through an Enterprise Java Bean? In the Access BE? What verification to the user is there that the record has been deleted? Has the version of the Java or web server been updated? Has the server OS been updated? Has Access been updated? Have any drivers been updated? ODBC? JDBC? Did somebody new within the process start work recently? New technician on the line? New DBA? New programmer? etc. etc.

There are so many things. You're there and are the only one who can see it all. So you need to give us information if you need help.

 

[sphynx]

Sorry should have been more specific, please bear with me as this is the first access database I have put together.

The records are deleted by an admin user via a password protected front end, they select the appropriate record in the results query and hitting the delete key, access flashes the normal warning about deleting the record, hit the yes button and the record disappears.

On reopening the query the record have reappeared!

I am the only person involved with programming & alterations, the normal access back door (shift) is disabled and requires a password input to make any changes to the database, i am therefore 100% confident that it hasn't been altered in any way without my knowledge.

Everything that is accessible via the front end is secure and protected

I have recently added some extra functions to the DB and an extra column into the results Query, this however is not a calculated field and simply pulls a linked number from a different table, so I cant see why this would be an issue?

As far as I am aware there have been no software or driver updates. i am using apache tomcat 6 within manufacturing open a connection with the access database to push the records via SQL into my results table. Tomcat is not configured to update on either of these computers so has also not changed

 

[neileg]

Has the query become non-updatable by adding your additional field?

 

[sphynx]

No the query is updatable.

I have fixed the problem now though, I had to remove the extra column and link that I had added to the query.

This then gave me the ability to delete records without them reappearing on reopening. I then rebuilt the extra column, references and links and all is fine.

Just another access random hissy fit, thank to those that posted replies

 

[neileg]

I wonder if this relates to referential integrity?

 

[georgedwilkinson]

I wonder if this relates to referential integrity?

With what we know now, I'd say "yes".