The issue is not creating tables, as Ican send DDL to every database I have
worked with without problem. The issue is creating the original database. To
completely avoid COM, you end up creating a database template (.mdb with no
tables) and copying it where you need it. You can then add objects to the
database, as long as they are definable in SQL (for example, forms are
objects you cannot write out in SQL, so you have to use Access objects (COM)
to set them up).
NOTE: I have not dinked fully with the Office .NET components. With these,
you may be able to do more of the creation, etc., of Office docs and files.
You note this is aimed at Office 2003 (maybe XP?), so it is not applicable
to all versions.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
*************** *************** *************** ***
Think Outside the Box!
*************** *************** *************** ***
"Tink" <Ti**@discussio ns.microsoft.co m> wrote in message
news:45******** *************** ***********@mic rosoft.com...
I have Googled this topic to death to the best of my ability and hope that
somebody here can help.
I do not want to have any COM dependencies in a project. For various
reasons, the application will use an Access database. Unfortunately, it
appears ADO.NET does not allow you to create a database and tables.
Everything I have seen seems to point to ADOX, but that requires an
ActiveX component which I extremely want to avoid.
Does anybody know how to programmaticall y create an Access DB and tables
in that DB without using a COM object?
Thanks in advance for any help.