Edward S Zuris
edzedz at comcast.net
Tue Apr 29 12:38:11 CDT 2008
Good advice William. I have done fair amount of work moving Access 2.0 and its compatiblity layer, to newer versions of Access. It is mostly grunt work. Some of the old API calls used in A2.0 and A97, like for tool tips, are now built into the newer versions of Msaccess. But it is grunt work. Boring grunt work. Though sometimes you just find out what the VBA code intent is, and do a re-write. If you can keep the project in DAO the cost will be less. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of William Hindman Sent: Tuesday, April 29, 2008 9:12 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Migrate 2.0 and A97 to XP: Advice and Cost??? ...97 to xp is just minor grunt work if the original coder actually did his job. ...but if the "97" code is really A2 code running under the 3.5 library then you can have a nightmare on your hands ...it all depends on the original coder, how much Access Basic used versus API calls, and how well commented it is/was. ...my practice is to give them a firm fixed price quote to assess the existing code and produce a proprietary report on what is actually needed ...then go from there once you have something real to deal with ...if you have the FMS diagnostics suite, this is usually something you can do in a few hours, produce reams of report paper on, and impress the hell out of them without actually killing yourself ...if you don't have the FMS Suite, good luck ...whatever you do don't give them a price without knowing exactly what you're taking on ...and make sure that the conversion project is extremely well defined in terms of additional reports, functionality, etc ...and that you have a firm understanding that any and all changes/additions past your original proposal are at additional cost. ...as to hourly rate, there's an article I wrote on the subject for the first dba newsletter which is still posted on the website ...nothing has really changed ...if you run the numbers your rate question should answer itself ...don't sell yourself short ...its better to starve in a rocking chair than to starve while producing code you sold short ...imnsho of course. ...hth :) William -------------------------------------------------- From: "Mark A Matte" <markamatte at hotmail.com> Sent: Tuesday, April 29, 2008 11:17 AM To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com> Subject: [AccessD] Migrate 2.0 and A97 to XP: Advice and Cost??? > > Hello All, > > A small company needs to have some Access DBs upgraded from Access 2.0 and > A97 to XP. > > They want to provide airfare and hotel...and pay hourly. > > The project will involve upgrading, some system functionality > modifications, and some new reports. Some of their current functionality > is "broken" (all the detail they had). > > Any suggestions to the approach, things to look out for in the migration, > or any advice? > > Also, what would be considered a fair hourly rate? > > Thanks, > > Mark A. Matte > _________________________________________________________________ > In a rush? Get real-time answers with Windows Live Messenger. > http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh _realtime_042008 > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com