Undo Multiple line Edits/Add/Delete in Sub form (Its possible)

  • Thread starter Thread starter Syed Ubaid
  • Start date Start date
S

Syed Ubaid

(I posted this issue and got a reply from Mr. Allen,
I am again posting this as I saw/use the solution of
the same issue.. )

Currently I m working in a organization where a MS ACCESS 97
database is used over a network. I some how make to view the
detailed structure of DB but couldn't read any code from MDE
(as it not viewable).

The developer has somehow (how??) managed to UNDO the
multiple line/record add/edits in subform without creating any temp
table.I check the DB while editing/adding but there was no temp
table.I contacted him for help but he has moved to Gulf. It seems
he managed UNDO of multiple lines/record in subform by some
piece of code. it might be TRANSACTION or some other way..
I can also send u the database, MDE & MDW for review if required
(DB requires specific settings like must be placed in D drive sharing
as ser_D...etc)

It shows possibility of UNDO via code...can u help me in that CODE..??


Syed
 
The developer has somehow (how??) managed to UNDO the
multiple line/record add/edits in subform without creating any temp
table.I check the DB while editing/adding but there was no temp
table.I contacted him for help but he has moved to Gulf. It seems
he managed UNDO of multiple lines/record in subform by some
piece of code. it might be TRANSACTION or some other way..
I can also send u the database, MDE & MDW for review if required
Click to expand...

The MDE file wouldn't do any good. The code is not hidden; the source
code is GONE, DESTROYED, removed from the database altogether.

I would guess that he is executing a Delete query to delete all the
records in the Subform's recordsource table which match the Child Link
Field value, and then another Update query to delete the mainform
record.

The effect will be the same as an Undo; but it's actually physically
removing existing records from the table. For a multiuser system this
could be problematic since you have no assurance that another user
hasn't perhaps seen and used the data between the time it was entered
and the "undo" occurs, but that seems fairly unlikely and there's no
way around it anyhow.
 
Back
Top