Access 2003 Macro won't run past first row

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

Guest

Whenever i run a macro, access never makes it to the second action. first
row/action deletes a table, second row/action imports a table. the problem is
that it never makes it to this second row/action even though the first is
successful. I usually just keep recreating the database or macro until it
works but i really need to know why this is happening.

I've recreated the database from scratch, lowered macro security to low.
disabled all security prompts. Please help
 
Post the full information about the macro's actions, including the
arguments' values.

How do you know that it never gets to the second action?
 
Thanks for replying Ken.

1.Action:DeleteObject, Object Type:Table, ObjectName:[TableName]

2.Action:TransferDatabase, Transfer Type:Import, Database Type:Microsoft
Access, Database Name:\\server\share\db.mdb, Object Type:Table,
Source:[TableName], Destination:[TableName], Structure Only:No

I know because this first row completes successfully deleting the table. the
second row, however, never makes it to the database even though the macro
closes with no errors. there's a few more rows to this but they may not be
relevent to this problem but let me know.
 
Just to verify that you don't have "warnings" turned off, insert the
SetWarnings action (with argument value of On) at the beginning of the
macro. Do you get a message then for the import step?

I assume that you're using generic names in the arguments that you've
posted? You don't actually have [ ] around the table names, do you?
--

Ken Snell
<MS ACCESS MVP>


commonkev said:
Thanks for replying Ken.

1.Action:DeleteObject, Object Type:Table, ObjectName:[TableName]

2.Action:TransferDatabase, Transfer Type:Import, Database Type:Microsoft
Access, Database Name:\\server\share\db.mdb, Object Type:Table,
Source:[TableName], Destination:[TableName], Structure Only:No

I know because this first row completes successfully deleting the table.
the
second row, however, never makes it to the database even though the macro
closes with no errors. there's a few more rows to this but they may not be
relevent to this problem but let me know.


Ken Snell (MVP) said:
Post the full information about the macro's actions, including the
arguments' values.

How do you know that it never gets to the second action?
Click to expand...
Click to expand...
 
Tried that (good suggestion), inserted a new first row, set
action:SetWarnings, had to set the argument value to Yes (yes/no). Second row
is supposed to delete a table but it never does.
Yes, those are generic names:)
 
It's often helpful to see the real names that you're using --- sometimes we
are able to identify typo problems, etc.

In your first post, you said that the second action, the TransferDatabase
action, was not "working". In this most recent post, you now say that the
DeleteObject action is not "working"? Are you saying that, in all
situations, the second action in the macro is not "working", regardless of
what action it contains?
 
Ken Snell (MVP) said:
It's often helpful to see the real names that you're using --- sometimes we
are able to identify typo problems, etc.

In your first post, you said that the second action, the TransferDatabase
action, was not "working". In this most recent post, you now say that the
DeleteObject action is not "working"? Are you saying that, in all
situations, the second action in the macro is not "working", regardless of
what action it contains?
Click to expand...
 
I'd post that as well but i'm sure that each row is correct because i've run
each individual row successfully. No second row will process although i've
created two dummy tables as a test, then created a macro with two delete
actions that work (go figure).
 
Back
Top