Updating to MDAC 2.8

From: Andy DF (PrivateType_at_vb.com)
Date: 08/27/04 

Date: Fri, 27 Aug 2004 09:31:16 +0200

Hi all,

I just updated the MDAC version on my developing machine to the newest 2.8.
Since I'm working on an app that is already installed on some of my clients
PC's, I was wondering if changing the project reference from 2.6 to 2.8 will
effect the updates that I will be sending out to clients.

Will binary compatibility be broken?
Are there issues I should be aware of?

Thanks, 

-- 
Andy,
pctos550@hotmail.com

Relevant Pages

  • Re: MDE and runtime
    ... but at this point I may be sending the app to clients with nothing more ... I have Access 2003 with VB Tools, so I have no way to compile to an earlier ... reference sits in the ...Office10 folder. ...
    (microsoft.public.access.devtoolkits)
  • RE: Windows XP and VFP 8.0
    ... This error message is not a VFP error. ... Have you contacted the developer to ask him what might prompt this error? ... >The app is served in a shared folver by a Win98 pc. ... Clients are WinXP, ...
    (microsoft.public.fox.helpwanted)
  • Re: Function name not found
    ... developing a big app in Access, and now that more clients want it, I find out ... Doug Steele, Microsoft Access MVP ... eliminate the need for the reference, ...
    (microsoft.public.access.modulesdaovba)
  • Re: Software inventory not working as expected
    ... > putting an app in the ARP is to create an entry in the registry under the ... > If you app can do it by running the MSI by itself, ... >>> Sounds like the clients have not received the policies containing your ... >>> LastWriteDate, Size, CompanyName, ProductName, ProductVersion, ...
    (microsoft.public.sms.inventory)
  • Re: Windows XP and VFP 8.0
    ... WinXP are not server operating systems. ... > and clients running WinXP. ... > The app is served in a shared folver by a Win98 pc. ...
    (microsoft.public.fox.helpwanted)