Wait Table - Table edit question

[dpw204]

Being new to Access (Running Access 2000) trying to work on some pre-existing applications, I'm trying to understand many things.

How do I launch a table editing session, and then display a reminder message to the user after they close the table edit session?

Existing Code which launches a list table for editing:

DoCmd.OpenTable "tbl_List"

Adding a msgbox as the next line of code, executes immediately, rather than waiting for the
table close.


Would another approach be better? Objective: Provide the user the ability to edit a table driven look-up list, while they're on a form, once they're done editing the table, display a message.

suggestion, guidance appreciated, as I'm relatively new to Access, have more experience with Paradox DOS, where the Wait Table command would address this type of issue...

Thanks,
John

 

[boblarson]

1. Editing what, pray tell? Data or the table structure?

2. You should be using forms for data entry/modification, etc. and not in tables directly.

3. If modifying table structure then I argue that your database is not properly designed and normalized as that should almost never occur.

 

[dpw204]

1. Editing what, pray tell? Data or the table structure?

2. You should be using forms for data entry/modification, etc. and not in tables directly.

3. If modifying table structure then I argue that your database is not properly designed and normalized as that should almost never occur.

The code is launching a table containing a list of mail-merge reports which the users can update. In reviewing the 10-commandments, it appears this is the wrong approach, that a subform should be launched. - I can see how that would provide event controls...

And yes, this application is way abnormal.... It's going to be a major pain to attempt to re-work it to a normalized database, though that doesn't bear on my particular question.

 

[jal]

I'm no good with Access forms, but as I recall, the gurus on this forum (like Bob) say that the BeforeUpdate event is used to cancel (or permit) a user to edit a record shown on an Access form. If you agree with the user's suggested edits, then I suppose you can fire a messagebox in that event which says, "Permission granted, updating the record now." If you disagree, you can cancel the update and fire a msgbox,"Invalid edit."

Maybe try searching the forum (or googling) for examples of BeforeUpdate.

 

[dpw204]

I'm no good with Access forms, but as I recall, the gurus on this forum (like Bob) say that the BeforeUpdate event is used to cancel (or permit) a user to edit a record shown on an Access form. If you agree with the user's suggested edits, then I suppose you can fire a messagebox in that event which says, "Permission granted, updating the record now." If you disagree, you can cancel the update and fire a msgbox,"Invalid edit."

Maybe try searching the forum (or googling) for examples of BeforeUpdate.

Thanks. Yes, that approach is working. Once I switched the code to not open a table, but instead open a form, I was able to add code to the form and use event triggers.