Hi yea,
I have rebuilt my PC three times in the last two days, If any one can help I would be grateful. I am using dreamweaver MX 6.1, I also use XP Pro with IIS, I set up my dir as usual in the wwroot but I keep getting the following error,
Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC Microsoft Access Driver] Could not use '(unknown)'; file already in use.

What or where am I going wrong, I have tried and tried and played with the permissions to no avail, is there some secret. I used to use PWS with no problems but now using IIS on XP Pro over the last few days all I get is error after error.

Can anyone enlighten me please please.

Kenny

Have you set up a ODBC connection in XP?

Yes Thank you,
I have set up the Connection in XP PRO and have downloaded all the update's from Microsoft, In my WWWRoot I have 2 Dir which I created, on htdocs for my ASP pages and another Private for my access database, I have given them both read write browse and created an application in IIS, I have done this hundredreds of times before but now it wont work, I think it must be the latest updates from Microsoft that changes the permissions or something, I am near to pulling my hair out. If I have the access database in the same dir as my asp pages then all seems ok but I need to have it in a seperate Dir and it worked before so why wont it work again. Thank you for the reply and all the help is greatly appreceited.

Regards


Kenny

<BLOCKQUOTE id=quote><font size=1 face="Verdana, Arial, Helvetica" id=quote>quote:<hr height=1 noshade id=quote>
Have you set up a ODBC connection in XP?
<hr height=1 noshade id=quote></BLOCKQUOTE id=quote></font id=quote><font face="Verdana, Arial, Helvetica" size=2 id=quote>

I am wondering are these problems stemming from my PC being NTFS instead of FAT32, wowa if so what should I do.

Regards


Kenny

I found it the fix is here, www.macromedia.com/support/dreamweaver/ts/documents/chge_access_permissions.htm#xpsteps th errors never happened with windows 98SE only XP pro , and only after I installed the latest patches to XP. So it appears the permission issue needs to be given a little more time to get it right in future. read fix at the above link.

kenny