[dba-SQLServer] Upgrade to SQL

[Stuart McLachlan]

If you just link the SQL Server tables using ODBC and the same table structures in both 
Access and SQL Server, you shouldn't need to make any changes to the FE apart from the 
links.

I have a couple of apps which have code to switch links to a local Access BE, a network BE 
or an SQL Server instance.   No conditional compiles or anythiing else.

 
> -----Original Message-----
> From: dba-SQLServer
> [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Rocky
> Smolin Sent: Monday, January 18, 2016 7:36 PM To:
> dba-sqlserver at databaseadvisors.com; 'Off Topic' Subject:
> [dba-SQLServer] Upgrade to SQL
> 
> Dear Lists(s):
> 
> The guy who acquired my product want to make a front end compatible
> with SQL server (and of course upgrade the back end as well). But he
> wants to keep both version of the product - SQL and Access.
> 
> I told him it really means two FEs because the SQL version is so much
> different than the Access version.
> 
> The app has something around 200 forms and subforms, on the order of
> 250 queries, about 150 tables about 1/2 of them in the back end, 1/2
> in the front, and lots and lots and lots of code. 
> 
> He wants to know if one FE can be devised to support both Access BE
> and SQL BE.
> 
> I told him about the conditional compile command which could compile
> just the statements you'd want based on a switch.  But given the
> number of differences in code between the two versions I cautioned him
> that it would be an awkward program to maintain.
> 
> I've never done that kind of conversion before so I'm wondering just
> how practical (or not) would it be to have one FE to handle both an
> Access and a SQL back end?
> 
> MTIA
> 
> Rocky
>