OK I got it to work with Microsoft Office 2003. It turns out in a install that never had a previous Office version that we do have the Microsoft Office XP Web Components. They are in C:\Program Files\Common Files\Microsoft Shared\Web Components\10 and we can just folow the directions for that version of Microsoft Office they have included in the article.
Now I changed the connection object slightly. I made a udl file and connected to data.mdb as a Microsoft Jet 4.0 OLE Provider to obtain the connection string and got this:
Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Inetpub\wwwroot\fpdb\data.mdb;Persist Security Info=False
As you can see the database data.mdb is in the FrontPage location for databases fpdb.
Also I removed the comments they have for adOpenStatic and adUseClient. I insure my server recognizes those constants by including:
<!--METADATA TYPE="typelib" UUID="EF53050B-882E-4776-B643-EDA472E8E3F2" NAME="ActiveX Data Objects 2.7 Library" -->
at the top of my global.asa. Normally we can include adovbs.inc to do this. Put this include in if you don't want to put the above in your global.asa. Well they used the actual constant values anyway.
Finally make sure the folder that contains the sample on the site has NTFS permissions to write for the users that have access to the folder and change the permissions in IIS Manager to write for that folder.
--
George Hester
__________________________________
http://support.microsoft.com/?scid=kb;en-us;264096
They give an explanation of the changes necessary for Office 10 (Microsoft Office XP). Can someone explain the changes necessary for Office 11 (Microsoft Office 2003)? Thanks.
