Hi all,
I am running a macro which imports 3 tables from a different .mdb file on
the same drive. However, I want the user to be able to run the macro
regardless of whether or not the table actually exists in the other .mdb.
In other words, the 2nd .mdb which I will be importing from is a station
where an intern enters checks into the computer. However, sometimes there
will only be 1 or 2 tables. As the DB admin, i want to be able to run the
macro to import the tables regardless of whether or not the tables actually
exist (i.e. - when the intern is finished with a batch of checks from a
particular day, she starts a new table for the next day).
Does anyone know if I can run the macro without getting the halt message
telling me the object I am trying to import doesn't exist?
Thanks in advance and let me know if I can clarify any of this, I know that
it may sound complicated.
-Rob
KARL DEWEY - 25 May 2006 17:27 GMT
Try setting condition to see if it exists.
> Hi all,
>
[quoted text clipped - 16 lines]
>
> -Rob
Rob - 25 May 2006 17:29 GMT
What condition could I use? Remember that it is looking in a totally
different .mdb to import the files
> Try setting condition to see if it exists.
>
[quoted text clipped - 18 lines]
> >
> > -Rob
KARL DEWEY - 25 May 2006 19:10 GMT
Use full path, database name, query for HasData.
> What condition could I use? Remember that it is looking in a totally
> different .mdb to import the files
[quoted text clipped - 21 lines]
> > >
> > > -Rob
Rob - 25 May 2006 19:31 GMT
I'm sorry I'm not quite sure that I understand. Can you please give me a
generic example?
Thanks
> Use full path, database name, query for HasData.
>
[quoted text clipped - 23 lines]
> > > >
> > > > -Rob