[AccessD] Upsizing

There is a utility from an Australian firm (Trigeminal, if memory serves)
that inspects your Access data and tells you to fix anything that may pose a
problem when upsizing (and there are more than a few gotchas). I don't have
it handy, but it is amazingly good at spotting potential problems. Once
you've attended to these, the Access upsizing wizard does everything
correctly. Visit the Trigeminal site and see if my memory is correct as to
creator.

Arthur

On Mon, Jan 10, 2011 at 6:17 PM, jwcolby <jwcolby at colbyconsulting.com>wrote:

> One thing you must do is get all dates handled.  Access and SQL Server can
> handle different ranges of dates and if the access dates can't be
> imported...
>
> You must look for dates before 1/1/1900 and if they exist get them to be
> after 1/1/1900.
>
> John W. Colby
> www.ColbyConsulting.com <http://www.colbyconsulting.com/>
>
>
> On 1/10/2011 3:15 PM, Jim Lawrence wrote:
>
>> Thanks for the info...
>>
>> The data importation is the key point and I have been playing around with
>> and eventually ended with Microsoft's SQL Server Migration Assistant
>> (SSMA)
>> for Access (http://tinyurl.com/37ltooy) to that end. It may be simple
>> once
>> it is configured properly but as of yet it is only sort of working(?)
>>
>> I have dragged all the queries and tables into a single MDB (no minor feat
>> as it required the merging two applications) and am hoping this time it
>> will
>> push/translate the objects through without a hiccup... (May have to
>> migrate
>> the master MDB from 2003 to 2007 to make it all work)
>>
>> This exercise was supposed to be quick and dirty. If can think of any
>> better
>> solution don't hesitate to enlighten me, ;-)
>>
>> After all this fun I am sure the client's site will be much easier to
>> configure...? Yeah...right...
>>
>> Jim
>>
>>
>>
>> -----Original Message-----
>> From: accessd-bounces at databaseadvisors.com
>> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart
>> McLachlan
>> Sent: Sunday, January 09, 2011 2:39 PM
>> To: Access Developers discussion and problem solving
>> Subject: Re: [AccessD] Upsizing
>>
>> I would just import all of the BE tables into SQL Server and then relink
>> the
>> FE using ODBC.
>>
>> I've got a couple of systems where I do something similar.  The FE
>> application can work with
>> either an Access or a SQL Server BE depending on the environment.   It's
>> simply a matter of
>> running some re-linking code to switch between BEs.
>>
>> --
>  AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>