[quoted text, click to view] "Grant" <anonymous@discussions.microsoft.com> wrote in message
news:002718C3-B9EE-4E81-AC49-7B845A3FE7CF@microsoft.com...
> Hi,
>
> I have a VB 6 IIS Application running as a compiled DLL under IIS 5.0 on
Win2K. It uses the ADO 2.5 library to give users OLEDB and ODBC access from
a browser, to various types of databases - mostly remote from the IIS server
itself.
[quoted text, click to view] >
> I've run into a problem that's referenced in an MSDN article "Debugging
your IIS Application" ... "Do not use an Access database on a remote
computer in your project. While this will work in debug mode, it will not
work when the application is compiled."
[quoted text, click to view] >
> Is there any kind of workaround that would allow access to a remote MS
Access database from a compiled (DLL) IIS Application?
>
> I've tried various means of access - setting up the remote Access database
as an ODBC database; using mapped drive letters; using the machine-based
name (\\remotemachine\databases\mydb.mdb) - but nothing seem to work on the
compiled DLL even though all of these methods work in the development
environment, as well as in the VB6 "Standard EXE" version of my software.
[quoted text, click to view] >
> Any help would be appreciated.
This might be helpful. I can't offer more because you don't explain what
"nothing seem to work" exactly means.
http://www.aspfaq.com/show.asp?id=2168 --
Tom Kaminski IIS MVP
http://www.iistoolshed.com/ - tools, scripts, and utilities for running IIS
http://mvp.support.microsoft.com/
http://www.microsoft.com/windowsserver2003/community/centers/iis/