MartyConnelly
martyconnelly at shaw.ca
Mon Feb 20 23:03:55 CST 2006
I wouldn't mind seeing the xml. Martin Reid wrote: >People say there are plans to enhance macros for MS Access but these plans >when implemented shouldn't hopefully kill VBA... > >havnt really looked at them yet but there is something called embedded macros in all the new templates supplied no vba at all. The templates themselves are pure xml files when you open them outside access. Each access object comprises an xml file a format file and a description file of some sort. A tool will be available which will shred an access db file into the required xml to permit you to create your own templates. If you want I can post a sample of the XML files for an object. > >Martin > >-----Unmodified Original Message----- >Ken, > >VSTO as far as I see creates COM Add-ins wrapped into .NET Framework "candy >wrappers" + different installation/deployment scenarios based on XML >manifest files... > >I may have missed something(please correct) but basically that's all... > >And new XML based file formats for MS Word and MS Excel - my easy guess is >that they use XML serialization/deserialization via MS XML Core Services >COM based DLL(s) to save/instantiate MS Word/Excel documents, which as all >we know consist of many instances of child objects. That format change >wasn't a heavy move on my guess - internally they still use the same >software... and no plans to rewrite in using .NET Framework... > >As for MS Access one can write COM/VSTO Add-ins for MS Access or just CCW >wrapped .Net class library .dlls - so I don't think we, MS Access >developers, are "out of the game" here... > >VBA will probably be with us and MS Access until MS Office exists - good >news for MS Access VBA developers! > >People say there are plans to enhance macros for MS Access but these plans >when implemented shouldn't hopefully kill VBA... > >Will they(MS) rewrite their COM based flagship software in foreseeable >future? - the doubts in that only grow here - VS.NET 2005 is even better for >COM native development than previous Visual Studio releases... > >I wanted to switch to C++/ATL/COM development - anybody has any good >projects there? :) > >Shamil > >----- Original Message ----- >From: "Ken Ismert" <KIsmert at texassystems.com> >To: "Access Developers discussion and problem solving" ><accessd at databaseadvisors.com> >Sent: Tuesday, February 21, 2006 1:00 AM >Subject: Re: [AccessD] FYI: Good news - VBA in Office 12 and beyond... > > > > >>In fact, if you look at Visual Studio 2005 Tools for Office, you'll find >>it has no built-in support for Access yet... >> >>http://msdn.microsoft.com/office/understanding/vsto/default.aspx >> >>As usual, Access lags behind its Office companions in terms of the >>latest development platform support. >> >>That means we'll be able to hang onto that juicy VBA goodness for at >>least one release beyond any of the other Office components. >> >>:) >> >>-Ken >> >> >>-----Original Message----- >>From: Shamil Salakhetdinov [mailto:shamil at users.mns.ru] >>Sent: Sunday, February 19, 2006 7:24 AM >>To: !DBA-MAIN >>Subject: [AccessD] FYI: Good news - VBA in Office 12 and beyond... >> >>http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=190669&SiteID=1 >> >>Shamil >> >> >>-- >>AccessD mailing list >>AccessD at databaseadvisors.com >>http://databaseadvisors.com/mailman/listinfo/accessd >>Website: http://www.databaseadvisors.com >> >> > > > -- Marty Connelly Victoria, B.C. Canada