Interdev and ODBC File DSNs

I've inherited responsibility for a set of web pages that use Active
Server Pages (.asp).  These .asp scripts in turn read and write an Access
database which involves setting up ODBC Data Source Names (DSNs).  On our
intranet, these pages used System DSNs.  Interdev 1.0 was used to develop
the .asp scripts, and it runs on the same machine as the IIS web server. 
It works fine.


Now I need to export or publish this set of pages to another web server
(going through firewall/proxies).  I do not have admin privileges on the
target NT machine for either the sysadmin or IIS admin.  I've been told
that I can use File DSNs on my local machine instead of System DSNs, and
when I export/publish from Interdev to the target machine that it will
create/modify the necessary files as appropriate for the target system. 
I am a novice at .asp and Interdev, and I am doing this in my spare time
(ha!).


The little time I have spent on this I have not been able to get it
working.  I've looked at the global.asa file and it has enrites such as


DBQ="<bigger>DBQ=D:\<<path>\dbfile.mdb;DefaultDir=D:\<<dirpath>;Driver={Microsoft
Access Driver (*.mdb)};DriverId=25;FIL=MS
Access;ImplicitCommitSync=Yes;MaxBufferSize=512;MaxScanRows=8;PageTimeout=5;SafeTransactions=0;Threads=3;UID=admin;UserCommitSync=Yes;"


Note that <<path> and <<dirpath> above contain a valid absolute pathnames
on my local system (.e.g., D:\dir1\dir2\foo.mdb, D:\dir1\dir2).


Do I need to edit the global.asa file by hand so these directory paths
are appropriate for the target, or will Interdev do this for me?  Should
I be using relative pathnames?


In setting up File DSNs, I noticed that .dsn files are created, which
contain DefaultDir and DBQ= entries similar to those in the global.asa
file (in the Sub Session_OnStart section).  The .dsn file DBQ= contains
the path to the .mdb file.  When using File DSNs, should the global.asa
point to the .dsn file, which in turn points to the .mdb?  Should
Interdev be updating both or either of the global.asa or .dsn files when
it exports to the target system (which has a different directory
structure).  I'm not even sure of the absolute path on the target since
the admin set up a virtual directory; the best I could do would be a
relative path without any drive letter.


Anyway, guidance or suggestions are appreciated.


Paul

	</bigger>

HWG: hwg-software mailing list archives, maintained by Webmasters @ IWA