For security, you will not see the SystemDSN name when accessing the site remotely. Create on the
site that you can see the list of SystemDSN, then copy the global.asa file into your local site,
then run tools | site setting | database to verify the connection.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
http://www.ycoln-resources.com
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
To assist you in getting the best answers for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
"Cheryl" <(E-Mail Removed)> wrote in message
news:547494B2-F121-4954-9B49-(E-Mail Removed)...
> ok.. ty.. and once again, apologies for previous post... being similar but
> was having internet problems...
>
> I created a system dsn on the server. That is fine.. but when I create a new
> database connection locally.. to use system dsn.. it can't find one...
> However, if I go to my remote web site and create a connection there.. it of
> course can see it. So, what am I doing wrong?
>
> "Thomas A. Rowe" wrote:
>
>> Only possible within FP if you set up a systemDSN. You host must allow you or create the
>> systemDSN
>> for you, otherwise you have use a separate database for each subsite.
>>
>> --
>> ==============================================
>> Thomas A. Rowe (Microsoft MVP - FrontPage)
>> WEBMASTER Resources(tm)
>> http://www.ycoln-resources.com
>> FrontPage Resources, WebCircle, MS KB Quick Links, etc.
>> ==============================================
>> To assist you in getting the best answers for FrontPage support see:
>> http://www.net-sites.com/sitebuilder/newsgroups.asp
>>
>> "Cheryl" <(E-Mail Removed)> wrote in message
>> news:7857ECD0-0A96-4C26-8B2B-(E-Mail Removed)...
>> > Using Frontpage 2003, how do I use a Access database store in fpdb folder
>> > from other subsites? I want to use same database for different things... I
>> > thought perhaps subsites for different departments so I can restrict access
>> > using site permissions...
>>
>>
>>