Access to MSSQL--Access project

I have a frontend .mdb file and a backend .mdb file. The backend needs to be upsized to SQL Server. The frontend needs to stay in Access but needs to be converted to an Access project (.adp file). I am an Access developer that is very familiar with the ODBC world but not so much when it comes to OLEDB and ADO. Also not familiar with MSSQL Server and the inherent Views and Stored Procedures that Access Jet-SQL queries would have to be converted to.

SPEED is the issue. This database needs to be as quick and responsive as Access is with ODBC. The reason it can't stay in Access is because the backend database has ballooned to almost 750,000 records. With with an Access project file interfacing via ADO natively to MSSQL, it's supposed to be very fast I'm told.

The frontend has about 90 recordsets that would need to be centralized into one recordset-creating function (like an include file on the web) as well as have its queries converted to Views and Stored Procs.

Any other suggestions would be very helpful. The budget for this project is $200. I have a 14 MB zipped file (the Access .mdb files) I would need to upload for potential vendors to analyze.

Skills: Visual Basic, Windows Desktop

See more: web frontend developer, mdb files, jet sql, adp web, adodb adp access, access frontend mssql backend, suggestions, stored procedures, stay, sql views, sql project , sql odbc, SQL Access, project, Project m, project developer c#, project c++, project budget, Procedures, mssql

About the Employer:
( 0 reviews ) Mesa, United States

Project ID: #10483