If you move to MSSQL 2008 or newer, the varchar(MAX) nicely replaces the Access TEXT data type. If you use the SQL Server import tools rather than the Access migration tools, you should be able to do "identity insert on" on auto increment columns and preserve their values.
-Carl V. On 11/5/2013 7:27 AM, Ben wrote: > Yep. That sounds familiar. And some of the auto incrementing features in > access don't convert well. Perhaps a more recent conversion package version > does a better job these days. This was about 9 years ago. > > Ben > >> On Nov 5, 2013, at 8:20 AM, Russ Michaels <r...@michaels.me.uk> wrote: >> >> >> Microsoft provide a free migration tool, as you are obviously on windows I >> would suggest going with MSSQL and not MySQL >> http://www.microsoft.com/en-gb/download/details.aspx?id=28763 >> >> the code changes are fairly minimal unless your app is huge, but if memory >> serves it is mainly issues with primary keys and TEXT fields to varchar >> fields you will have to deal with. >> >> >>> On Tue, Nov 5, 2013 at 3:06 PM, Ben <b...@webworldinc.com> wrote: >>> >>> >>> Hi Russ >>> >>> For those of us who have been out of the loop for a while, can you suggest >>> easy to implement alternatives to 32 bit MS access? I did a conversion of a >>> DB to SQL server some years back and that was painful. >>> >>> Ben >>> >>>> On Nov 5, 2013, at 7:52 AM, Russ Michaels <r...@michaels.me.uk> wrote: >>>> >>>> >>>> well someone has to say it... >>>> but why the frack are you still using MSACCESS when there are so many >>>> better/free alternatives? >>>> you know the Jet driver (which is what you use to connect to MSACCESS) is >>>> no longer supported by Microsoft and ha snot been for years and only runs >>>> in 32 bit, and as such does not work on modern 64bit OS (without lots of >>>> hacking to get it to run in 32bit mode), which is Windows Server 2008 >>>> onwards, there is no 32 bit windows any more. >>>> >>>> >>>> >>>>> On Tue, Nov 5, 2013 at 2:44 PM, <> wrote: >>>>> >>>>> >>>>>>> I have robot updaters and inserters too (made all the more robotic >>> with >>>>> the >>>>> help of cfdbinfo figuring out the field types), >>>>> >>>>> This is what I do, but using my own CFX_ODBCinfo I developped years >>> before >>>>> cfdbinfo was available, >>>>> and I'm still using it because cfdbinfo doesn't work for Access >>> databases. >>>>>>> Debugging is miserable with a layer of >>>>> code in the middle and straightforward without. >>>>> >>>>> Right, I think I'm going to improve my CF_INSERT tag by generating the >>> SQL >>>>> code in the tag. >>>> >>> >> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:357048 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
