The real problem is that Oracle, Sybase, Informix, Raining Data, MySql all
have slightly different versions of sql. So often scripts for one system
will NOT work on anther system. Further, some of those databases don't have
referential integrity built in, and again thus the "constraint" syntax is
again different.
Further complicating the matter is that the scripting language in ms-access
is actually Visual Basic!
There are number of people who have cobbled together some solutions that do
read sql ddl commands...but as mentioned...all venders are different anyway.
You can start up a code module, and either paste in your ddl commands (but
you must wrap that ddl in vb code...the ddl must be put in a string
variable). Perhaps even better would be to write a small piece of code to
read the text script and execute the ddl.
However, if it is only 10 or 15 tables...then I would use the cut and paste.
Just open up the query builder, and switch to sql view. Then past in your
sql, and then whack the execute button. You will have to paste ONE ddl
command at a time (you execute multiple sql commands in the query builder).
However, like I said, with only 15 or 20 tables...then this would be faster
then trying to write some VB scripts anyway.
Besides the query builder will give you some syntax checking when you try to
run.
You can also use the ms-access command line prompt, and go:
currentdb.Execute "create table tblCustomer (FirstName text, LastName text)"
I would first give the sql query builder a try, and paste in one create
table at a time.
