[dba-SQLServer] Upgrade to SQL

[Rocky Smolin]

Thanks Dan.  It's just in the planning stage at the moment.  SO no hurry on
the code.  But if you send it, I'll forward to the developer to have on
hand.

They have to make a strategic decision to go for this upgrade.  As you know,
it ain't a spit and a lick.  And will take some dough as well to finance
that development.  And it puts them into a different market segment which
will mean some different marketing, sales, and support issues.  

Best,

Rocky Smolin
Beach Access Software
858-259-4334
www.bchacc.com
www.e-z-mrp.com
Skype: rocky.smolin
 




-----Original Message-----
From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On
Behalf Of Dan Waters
Sent: Monday, January 18, 2016 6:09 PM
To: 'Discussion concerning MS SQL Server'
Subject: Re: [dba-SQLServer] Upgrade to SQL

Hi Rocky,

I have code which does what you are describing.  The FE retrieves
information from a config file to learn if the BE is SQL or Access.  If
needed, one of two sets of table links (one is Access the other is ODBC)
gets named correctly, the other gets a prefix to make it not usable.  In my
situation, the two BE's each have the same set of identically named tables -
yours doesn't.  Still, I'll send you this code and perhaps you can get
something out of it.  However, I'll have to wait till Wednesday - hope that
will work OK.

Dan

-----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
 
 
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com


_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com