John W. Colby
jcolby at colbyconsulting.com
Mon Dec 1 19:39:08 CST 2003
But have you tried it? I seem to remember issues where if you compile in XP, trying to run in A2K would cause page faults, requiring a compile in A2K, then no page faults. Something about the VB6.DLL entry points differ between XP and 2K John W. Colby www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of William Hindman Sent: Monday, December 01, 2003 8:24 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] XP developer, Office 97 and a changing OS ...seamlessly? ...do you know of any piece of MS software that does anything "seamlessly"? ...just asking ...know the answer :) ...but short of that, yeah ...you can work with an A2K mdb in XP and it will maintain its compatibility ...HTH :) William Hindman Government is not reason, government is not persuasion, government is force. It is a dangerous servant." G. Washington ----- Original Message ----- From: "John W. Colby" <jcolby at colbyconsulting.com> To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com> Sent: Monday, December 01, 2003 7:52 PM Subject: RE: [AccessD] XP developer, Office 97 and a changing OS > William, > > Can you seamlessly work with A2K databases and importantly, libraries? I > would like to move to XP for all development if I can do my A2K development, > compile, compact and send to my A2K clients without any problems. I have my > framework lib to consider as well. > > John W. Colby > www.ColbyConsulting.com