G
Gary Walter
I wouldn't use a macro.....
Add a command button to any form.
In Properties of that command button,
change its name to
cmdDeleteDups
then scroll down until you find the Click event
for that command button...
double-click in white box next to it
which should cause change to
"Event Procedure" and a little box
at the right side with 3 periods.
Click on that little box to go to
a code skeleton for the click event
for that command button.
Add the code I gave you into
code skeleton Access created.
Click on save icon, then Debug/Compile
from top menu to make sure all correct.
(be sure to delete code from module
wherever you had it previously)
Add a command button to any form.
In Properties of that command button,
change its name to
cmdDeleteDups
then scroll down until you find the Click event
for that command button...
double-click in white box next to it
which should cause change to
"Event Procedure" and a little box
at the right side with 3 periods.
Click on that little box to go to
a code skeleton for the click event
for that command button.
Add the code I gave you into
code skeleton Access created.
Click on save icon, then Debug/Compile
from top menu to make sure all correct.
(be sure to delete code from module
wherever you had it previously)
ppc said:It has worked extremely smooth.Thanks for you great help.Just one thing
can I
run the module directly instead of calling it from a Macro with action
"OpenModule".
In my module section I am having correctly compiled module as per the code
given by you.But the Run button on the left side is not activated.
regds,
prasanna
Gary said:"Gary Walter" crappily typed:
[quoted text clipped - 3 lines]ErrorHandlerExit:
Set dbs = NothingResume ErrorHandlerExit
End Sub
should be
Set db = Nothing