[AccessD] FW: Converting Access to SQL Server

Collins, Darryl Darryl.Collins at anz.com
Thu Sep 17 00:10:25 CDT 2009



I can see how part of this could work nicely, but converting all your
Access (or SQL) queries to SQL Server Side Sprocs?  No idea how (or if)
they would have managed to pull that rabbit out of the hat.

Interested to see what people have to say.  Could be a good product to
watch though...

Cheers
Darryl.

 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Thursday, 17 September 2009 2:55 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] FW: Converting Access to SQL Server

Anyone know anything about this product?
 
Rocky
 

  _____  

From: Jeff Todd [mailto:jtodd at convertu2.com]
Sent: Wednesday, September 16, 2009 1:20 PM
To: rockysmolin at bchacc.com
Subject: Converting Access to SQL Server


Hi Rocky,

 

I found your contact information on the user group web site.  As an
Access
developer and consultant I thought you would be interested in hearing
about
a new software solution that converts Access to SQL Server.   It is
called
2SQLT. 

 

Our software, methods and process provides a very robust conversion
solution
which fully converts a Microsoft Access database into a Microsoft SQL
Server
database.  Most developers providing this service use the Microsoft
Upsizing
Wizard or SSMA (SQL Server Migration Assistance for Access) to do a
simple
linked tables conversion.    A simple conversion might be adequate for
some
applications, but not for others.  Our approach fits in between this
simple
conversion and an expensive and time consuming rewrite of the front end.

*	With 2SQ the result is an Access front end (NOT ADP) that is
converted to a fully SQL compliant front end and linked to the new SQL
backend.   

*	Client side processing is eliminated from the application and
all
processing now takes place on the backend server.   

*	Converting with 2SQL reduces the role of the Access JET engine
to a
simple connection object using ODBC.  

2SQL recognizes over 80 categories of Conversion Issues which relate to
Table Schema & Data, SQL Statements, SQL Server Objects, ODBC Connection
Objects, Optimization of Data Objects, and the VBA Framework and
automatically applies over 90% of the necessary software changes saving
hours and hours of manually finding and coding changes.  Some manual
conversions will still be necessary, but the conversion reports and
documentation we provide makes this cleanup work very manageable. 

 

Conversion projects with 2SQL become affordable for the client and will
be
completed in much less time.  The converted application can now take
advantage of all the benefits of being fully migrated to the SQL
platform
and without the expense of a complete rewrite.    

 

If you would like to know more I can send you a document which describes
our
Partner Alliance Program and our Technical Reference Guide which
describes
the process and all of the Conversion Categories and Issues the software
automatically converts.  If you do not want to receive any more email
from
us please let me know and I will remove you from our contacts list. 

 

Best regards,



Jeff Todd 
Business Development Consultant 
ConvertU2 Technologies Pty Ltd 
151 Coolidge Avenue, Suite 713 
Watertown, MA 02472 USA 

T +1 617 335 6679 
E jtodd at convertu2.com 
www.ConvertU2.com 


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

"This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential,  may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ National Bank Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."




More information about the AccessD mailing list