David McAfee
davidmcafee at gmail.com
Fri Jan 20 11:57:21 CST 2012
Move them over to an A2K ADP. It should be fairly simple. On Fri, Jan 20, 2012 at 9:48 AM, jwcolby <jwcolby at colbyconsulting.com>wrote: > My client is moving to SQL Server at my persistent prodding. They have > outgrown Access database containers, we have had to split their original > single Access BE many times and now have about 6 different BEs with as much > as 800 megs of data in some of them (after compact / repair). "Another > user has locked this record" kinds of issues. All that stuff. > > So we are slooooowly moving the database to SQL Server. > > The problem is that they remain firmly mired in Access 2000. Yep. Sigh. > > The biggest issue with Access 2K from the perspective of SQL Server is > that forms cannot be bound to recordsets and still be editable. > > So I am searching for a way to emulate what has always mostly worked, yet > at least maintain the current speed (not great) or speed things up. > > I have been using SQl Server with Office 2003 for a long time and it works > very well but I don't have that here. I am considering trying to use > Access 2007 runtime, which I am using in other places and seems to work > quite well. The biggest problem with doing that for this client is simply > that the application is *very* complex and I program "to the metal". When > something doesn't work in runtime, it is extremely difficult to > troubleshoot. > > So I am looking for thoughts on my predicament, and how you may have > handled a similar situation. > > -- > John W. Colby > Colby Consulting > > Reality is what refuses to go away > when you do not believe in it > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/**mailman/listinfo/accessd<http://databaseadvisors.com/mailman/listinfo/accessd> > Website: http://www.databaseadvisors.**com<http://www.databaseadvisors.com> >