Yes - the second situation they mention is the one I was talking about. You basically have to make it so that the user account used by the application has rights and access on the computer with the tables. You can do this by either changing the user account used by the application to one with rights, or giving the IUSR account on the web server rights to the tables. I recommend the first option. It's simply a matter of creating a user account, making your application uses it when run, then giving it rights to the tables directory on the other machine. Steps 1 and 3 are simple admin functions. Step 2 may require you go into DCOMCNFG (run DCOMCNFG on the web server and see if it shows up on the list of applications - if it's there, modify it by double-clicking it and going to it's 'identity' tab and defining the user). Unfortunately, we'll need to know more about your setup before we can give you more detail.

HTH

>Michael - thanks for the reply. I dug deeper into Microsoft's Knowledge Base and came across the exact symptoms: http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q175801&
>
>Unfortunately, I am not a network guy, and the workarounds don't make any sense to me. Hopefully I will find an IIS5 for Dummies book that might hold my hand and give me step by step instructions on how to do this.