Data access page only opens on 1 shared drive?

[Beeawwb]

Hi everybody,

Really perplexing problem at the moment. A colleage interstate has developed
a database and corresponding data access page which works fine for them.
We've been sent it locally and I've been asked to set it up here. The problem
is, it only works if I open the HTA file from a mapped drive S:\

If I open it from a mapped drive G:\ or N:\ (where it will be used) it
doesn't grab any data. Even weirder, if I open the HTA for editing, it can't
connect to the MDB if I open it from any location apart from S:\.

For the record, the database connection string doesn't refer to a mapped
drive, it uses \\sadlfs004\deptdata\shared\productivity\productivity
sa\exgratia.mdb I've gone through every inch of the Script Editor, looking
for a reference to S:\ and I can't see anything.

Does anybody know what might cause a data access page to only connect to
it's host data by a specific mapped drive? Any ideas how I might solve this?

Cheers,

Bob

 

[Ken Snell \(MVP\)]

Check the Connection property for each data access page in the database
file. Each page also has its own connection, and likely the pages were
developed on a computer that used a mapped drive S. Thus, those pages would
have the S drive hardcoded into their structure too.

You must change the connection property of each page manually and
separately.

 

[Beeawwb]

Hi Ken, thanks for your reply.

The database contains 1 mdb and 1 hta, so I've only got the 1 page to check.
I've checked the connection property and ensured that it's referencing the
\\sadlfs004\ string.

As for the development of the database, it was actually developed on a
mapped drive Y:\ (by my interstate colleague) and S:\ is just used for my
local development purposes.

Thanks for your ongoing assistance,

Bob

 

[Ken Snell \(MVP\)]

If you've checked the connection property for the data access page object
(not the database), and it's the right string, then there must be another
connection that is being used somewhere within the page which is using the S
drive.

I unfortunately don't have another idea for you to try.

 

[Beeawwb]

Hi Ken,

Just today I've worked out that providing a shortcut to \\sadlfs004\etc
instead of G:\etc will provide a working HTA file. Obviously, not the best
solution in the universe but it gets my staff online and using the database.

Given that Data Access Pages aren't really supported (they've been taken out
of Access 2007, haven't they?) I'm inclined to just take a "It's working,
deal with it" approach and try and work out some better way of using these
databases in the future. Peril of using the work of others I guess!

Thanks again for your time,

-Bob

 

[Ken Snell \(MVP\)]

Hi Ken,

Just today I've worked out that providing a shortcut to \\sadlfs004\etc
instead of G:\etc will provide a working HTA file. Obviously, not the best
solution in the universe but it gets my staff online and using the
database.

Sometimes, finding a workaround beats trying to find the "real answer" <
GRIN >. Been there and done that.

Given that Data Access Pages aren't really supported (they've been taken
out
of Access 2007, haven't they?)

Yes, they've been deprecated.

I'm inclined to just take a "It's working,
deal with it" approach and try and work out some better way of using these
databases in the future. Peril of using the work of others I guess!

See first sentence above.

Thanks again for your time,

You're welcome.