Again, I'm wondering, how are you getting the scale and precision for numeric fields from Access? I have been getting hosed by an OLE error everytime I try to get Access specific properties (which are custom and within the Properties collection for Field objects).

I don't see a problem with working with DAO as long as Access and/or Office is installed on the computer; although, if you are going to handle some of the enhanced stuff in Access 2000 or better, like Project files, you're gonna want to switch to ADO because (I think) DAO is Jet-specific and the DBEngine in Access 2000 can run SQL, MSDE, and Jet depending on the host database type.

>Right now my error trapping is minimal. I do have some in the VB code that traps errors during the creation process but it is pretty basic... puts a general error message and the message from the error number. As of yet does not offer decent recovery. I've pretty much just warned of possible problems in the notes for the program. Cowards way out! < vbg >
>
>I also look for some types of things before I send the info to the dll file. Stuff like.. to many fields, use of General fields ( I don't even try to do them ), strange characters in name, use of reserved words in names,etc. The last one I found out the hard way. In VFP you can (not a good practice but you can) have a field called "date". I found that this would crash the table creation process in my dll.
>
>In the VB dll I'm using DAO to provide some backward compatability with Access 97 files. I could not get any of the ADO created files to work with 97. Could have been my problem but I just gave up and used DAO. Not as "sexy" as ADO but it works.
>
>I will probably add an option pretty soon to use stuff specificaly for the creation of Access 2000 files.