delete confirmation on pushing delete button

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

hello
i add a delete button into a form that does not give me the confirmation
message after pushing it...is there anything i can do to fix it?
thanks
 
does this mean anything ?

Private Sub Command74_Click()
On Error GoTo Err_Command74_Click


DoCmd.DoMenuItem acFormBar, acEditMenu, 8, , acMenuVer70
DoCmd.DoMenuItem acFormBar, acEditMenu, 6, , acMenuVer70

Exit_Command74_Click:
Exit Sub

Err_Command74_Click:
MsgBox Err.Description
Resume Exit_Command74_Click

End Sub
 
i think db its behave a little strange. i did check that option and still
deleting without confirmation.
 
Are you turning off record changes anywhere in VBA code? If not, try the
following as a potential fix:

Create a brand new database and immediately disable the NameAutocorrect
feature (see: http://allenbrowne.com/bug-03.html for reasons why you want to
do this). Verify that you have Confirm Record changes selected under Tools >
Options | Edit/Find tab. Then import all objects from the suspect database
into the new database, one group at a time. In other words, import all tables
(but not linked tables), then import all queries, then all forms, etc. While
Access will allow you to import all objects in one operation, the experts at
FMS, Inc. (a Microsoft Partner), have stated that it is best to import
objects one group at a time (Reference:
http://www.fmsinc.com/ubb/Forum12/HTML/000285.html).

Recreate any linked tables from scratch. Access can cache a lot of
information about linked tables, which may no longer be valid, so it's always
best to recreate the linked tables from scratch. When importing local tables,
make sure to check the option to import relationships, menus and toolbars,
and import/export specs. If any of the local tables in the source DB are
hidden, you'll need to first unhide them. You will need to set the checked
references to match the source database, along with any startup options set
under Tools > Startup. Going through this process often times solves
corruption problems, because you get a new set of the hidden system tables
(the tables whose names start with "MSYS"). These system tables are updated
appropriately as you import objects.

This may sound like a lot of work, but it really isn't. Creating a new
container DB, disabling NameAutocorrect, importing all objects one group at a
time, re-establishing any linked tables, setting startup options, and setting
references to match the source DB is usually a fairly quick procedure. When
you are in the Visual Basic Editor, in order to check that the references
match the source DB, you should do a Debug > Compile ProjectName as well.



Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Back
Top