Up sizing study

[FuzMic]

Hi members

I had avoided moving away from Access02/03; I was just comfortably enjoying the .mdb even avoided using .accdb from 07. The reason being I feel so good staying in my comfort zone; living with familiar things yet get the job done. At the back of my mind is "small is good" recognizing the eventual point of diminishing return when a system grows huge.

But now with some prompts from members who asked me why I stay on the old place, I down loaded SQL Server 2017 and try my hand on it. My last encounter with SQL Server Express was 2005. At that time I used to be able to up size a mdb to the SQL Server using its database tool. This don’t seem to work any more from A03 up to A2013. What’s happening?

I am now able to import an mdb into a SQL data base going through OLE DB Provider for SQL Server from the SQL Srv 17 Import / Export 32 bit option.

When I look into the ODBC Admin in win10 v1709 I now see 4 drivers.

1. ODBC Driver 13 for SQL Server
2. SQL Server
3. SQL Server Native Client 11.0
4. SQL Server Native Client RDA 11.0

Which ODBC driver do I use to connect a mdb to the SQL Service?
Can i use OLE DB Provider in Access & how to do it?

Can some of my experts friends enlighten me in my unfamiliar environment i just got in?

 

[FuzMic]

Sir you have always gave the most valuable practical advice, THANK YOU SO MUCH.

 

[The_Doc_Man]

FuzMic, just for the record, Pat is a "ms.", not a "mr."

 

[FuzMic]

Sorry Pat, thousand apologises.