Are you using Microsoft Access as your database?  If so, then you are in a
bind.  Access stores path information to your local drive.  If you are
developing on one machine and deploying to a remote machine then you need to
make sure the Access database is in the exact same path on both machines.

The workaround to this is to never use DTC's.  They are evil.

A DTC carries a LOT of baggage as far as code goes (just look at
_ScriptLibray and see for yourself).  Also, DTC's are not scalable.

I would avoid them completely and code the ASP/HTML by hand.  It will save a
lot of frustration later when you start hitting the limitations of DTC's.

Also, if you use a third party host 90% of them that support ASP do NOT
support DTCs on their servers.  That should tell you something right there.

Brian Matsik, MCSD/MCT
President and Senior Consultant
Object Oriented Consulting Services, Inc.
www.oocs.com
-------

Author: "MCSD Fast Track: Solutions Architecture", New Riders
Co-Author: "Professional ADO 2.5", Wrox
Co-Author: "VBScript Programmer's Reference", Wrox
Co-Author: "Professional Visual InterDev 6 Programming", Wrox
Co-Author: "Professional Access 2000 Programming", Wrox
Co-Author: "Beginning SQL", Wrox

-----Original Message-----
From: vhs60w@h... [mailto:vhs60w@h...]
Sent: Saturday, May 12, 2001 3:06 PM
To: Interdev_Programming
Subject: [interdev_programming] global.asa connection ok in localhost
fails on remote server


Using Interdev global.asa in a localhost project, I have generated
different connections (native provider, filedsn, machinedsn, etc.,
all of which worked. But the connection strings in the application
onstart subroutine all reference paths on my system.

I have been unsuccessful in accomplishing connections on a remote
web server referencing DSN's created by the server administrator
to point to the database file on the server.

While connected to the server, I can see the web connections
being made remotely, i.e., messages "updating, etc.,etc....",
but the resultant global.asa still contains references to
files on my hard drive, so any asp page referencing the connection
fails.

What needs to be done to create the remote web connection in
global.asa on_start so that DTC recordsets can be created with
the same drag and drop that works on localhost?