Hi,
I'm trying to run queries on an access database through code in another database (this is because the database is too big to sit in one access db and so i've had to split it, but i still want only one 'user interface').
I'm using DAO to do this just now, using the
database.execute("...")
command to execute sql code on the 'remote' database.
I'm having problems because i can't use the 'set warnings off' command that i would have used in a macro to stop an error occurring when I make tables which already exist (i.e. to have it automatically replace these tables). I've tried 'DROP'ing the tables before i run the above make table code, but I'm finding this causes the remote db to top out at 2GB. I presume deleting tables before replacing them instead of setting warnings off defragments the database more?
I know about the docmd.setwarnings code but to my knowledge this can only be performed on the currently open (or active) database... So, how can i get my
vb to stop falling over when it tries to create a table (in a remote db) which already exists, and just replace it instead?
Any help anyone can give would be MUCH appreciated!
x