[AccessD] was SQL Server queries - appending strings

>An alternative to the other suggestions - which very quickly will turn your
job into a major project - you can connect to the server via ODBC.

And that is exactly what is going to happen.  There are enough reasons to
move the data store to SQL Server to justify doing that much.  As for moving
to an ADP, I have a framework that implements hundreds of behaviors that are
totally "automated" and allowed me to build the FE and it's functionality in
1/10th the time it would take to do it form by form implementing the same
functionality.  Because of this, the framework has to be modified to be
modified to be ADP friendly.  I do things like:

SELECT [Somefield] from Sometable WHERE SomeColumn LIKE
SomeForm!SomeControl.

These statements return EDITABLE recordsets in Access.  I use these EDITABLE
recordsets EVERYWHERE.  As we all know, this simply doesn't work in SQL
Server.  Until I can get around that obstacle in SQL Server, moving ANY
project to SQL Server will be non-trivial.

John W. Colby
www.ColbyConsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Gustav Brock
Sent: Sunday, February 01, 2004 4:07 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] was SQL Server queries - appending strings


Hi John

> Now that I am changing to SQL Server I have to get the server doing more
of
> the work - the whole point is of course to speed things up.  For technical
> reasons (a whole SLEW of reasons) going to an ADP is NOT an option any
time
> in the near future, if at all.

[snip]

> What are my options here?  Do I have any?

An alternative to the other suggestions - which very quickly will turn
your job into a major project - you can connect to the server via
ODBC. Not fancy neither sexy and lacking "MS coolness", I know, but it
works; your efforts will minimize to moving only the tables to SQL
Server and walking through your code adding some dBSeeChanges ...

Of course, this depends on the client and his priorities. Does he wish
quickly to move the data to SQL Server? Does he pay for your time
turning the current app into an ADP (which is the "right" thing) or is
that in his eyes just a "learning experience" for you?

/gustav

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com