[AccessD] Upgrade to MySql

Steve Goodhall steve at goodhall.info
Fri Aug 6 10:36:18 CDT 2010


  BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; }I
don't think that you will need to change anything that will work
through ODBC.  Once you get a recordset you should be OK for Move,
Add, etc.  In some cases you might want to rewrite things to be more
efficient.  The biggest problem you can expect is if you have a lot of
Access generated forms that work against complete tables or queries. 
These are likely to lock too many rows on the server side.
 I would put together a small prototype to test the limits before
jumping into the conversion.
 Regards, 
 Steve Goodhall, MSCS, PMP 
 248-505-5204 
 On Fri 06/08/10 11:15 AM , "Rocky Smolin" rockysmolin at bchacc.com
sent:
 Steve:
 Thanks for the reply.  
 Yes it's an Access BE so all the communication from the front end
then must
 be done via ODBC, yes?  
 Do all the DAO methods - FindFirst, MoveFirst, .AddNew, .Esdit,
.Update, etc
 - need to be reprogrammed?
 TIA
 Rocky
 -----Original Message-----
 From: accessd-bounces at databaseadvisors.com [1]
 [accessd-bounces at databaseadvisors.com [2]] On Behalf Of Steve
Goodhall
 Sent: Friday, August 06, 2010 7:35 AM
 To: Access Developers discussion and problem solving
 Subject: Re: [AccessD] Upgrade to MySql
   BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px;
}Are you
 currently using an Access BE database or some other RDBMS?  I have
just
 started playing with MySQL but I have done several conversions to
MSSQL.
 You will need to set up an ODBC connection to the MySQL database and
link
 the tables.  There are probably some subtle difference in the SQL so
you may
 need to do a lot of testing.
  Regards,
  Steve Goodhall, MSCS, PMP
  248-505-5204
  On Fri 06/08/10 10:22 AM , "Rocky Smolin" rockysmolin at bchacc.com
[3]
 sent:
  Deal List:
  I have a client with a rather large application who is considering
 upgrading  the back end to MySql.  
  Object:
  ~100 forms
  ~150 queries
  ~75 reports
  Lots of code modules with many lines and lots of CBF.
  The app uses bound forms and lots of DAO.  
  Question is, of course, what is involved in converting this front
end to
 work with a MySQL back end?
  MTIA,
  Rocky Smolin
  Beach Access Software
  858-259-4334
  www.e-z-mrp.com ;
  www.bchacc.com ;
  --
  AccessD mailing list
  AccessD at databaseadvisors.com [6] [1]
  http://databaseadvisors.com/mailman/listinfo/accessd
  Website: http://www.databaseadvisors.com
 Links:
 ------
 [1] AccessD at databaseadvisors.com [7]
 --
 AccessD mailing list
 AccessD at databaseadvisors.com [8]
 http://databaseadvisors.com/mailman/listinfo/accessd
 Website: http://www.databaseadvisors.com
 -- 
 AccessD mailing list
 AccessD at databaseadvisors.com [9]
 http://databaseadvisors.com/mailman/listinfo/accessd
 Website: http://www.databaseadvisors.com
 

Links:
------
[1] mailto:accessd-bounces at databaseadvisors.com
[2] mailto:accessd-bounces at databaseadvisors.com
[3] mailto:rockysmolin at bchacc.com
[4] http://www.e-z-mrp.com
[5] http://www.bchacc.com
[6] mailto:AccessD at databaseadvisors.com
[7] mailto:AccessD at databaseadvisors.com
[8] mailto:AccessD at databaseadvisors.com
[9] mailto:AccessD at databaseadvisors.com



More information about the AccessD mailing list