Access 2003 reference for accessing SQL Server 2012 database 1

[glgcag1991]

I have the daunting task of converting a 12 year old Access 2003 database (which was originally built in 2000) to work with a SQL 2012 backend. (Once that's done, I will begin rebuilding the forms and reports in ASP.NET). I tried using the existing DAO code but there were error tables that were created due to data truncation in some fields. DAO isn't going to work- I have to use ADO.

So, first issue: should I use 2.8? I have one XP computer left, the rest are Win7 and my understanding is I'll need 2.8 for the XP user. If not, what version of ADO is recommended. (I'll upgrade the one XP computer if there's a more stable version that is Windows 7 only.)

Second issue: I'm setting up references to ADO 2.8 but I notice there is a library reference, a recordset library reference and DDL & Security reference. Do I need to reference anything other than the 2.8 library or should I reference all three?

Thank you for the help, I appreciate it!

 

[vbajock]

I've found ver 2.6 to be the one most compatible with a wide range of Windows operating system.

If you are just manipulating table data, you need the ActiveX Data Objects Library, and this is usually the only thing I reference. DDL&Security is needed if you intend to programmatically change table structures, add indexes or read meta-properties, thing rarely needed on a typical Access project, Google ADOX for more info. ADOR, the last one, is useless, at least to me, it is supposedly a "lightweight ADO", so I leave it to the lightweights.

 

[glgcag1991]

vbajock,

Thank you for the reply! That was exactly the info I needed! I was looking at some forums that discussed issues with 2.8 and how it caused errors on XP machines if the mdb was compiled on a Win7 machine, so I assumed an earlier version would be better. Thanks!