[quoted text, click to view]

Oh! Linked tables! I've never gotten them to work. This article may contain
a reason:

http://www.trigeminal.com/usenet/usenet025.asp?1033

However, it's a very old article whose information may be out-of-date.

The only suggestion I can make is to use the Jet OLE DB Provider instead of
ODBC. See www.carlprothman.com for examples of OLE DB connection strings for
Jet.

Bob Barrows

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

A note before starting: I mention DBase files in this post. This is due to
the files being DBF format, which was originally created by DBase. The actual
files could have been created by Paradox, FoxPro, Advantage or a variety of
other programs that have adopted the basic format (generally with
extensions). As I am not sure what program actually created these files (not
evident in the post, AFAICS), I am calling them DBase files.


Running through the thread, I can see a couple of issues.

1. I would move to OLEDB instead of ODBC. If for no other reason, you will
speed up the application by removing one layer in ADO.

2. Is there anyway to directly access the DBase files? Linked tables also
add another layer. In the case of linked tables, you are setting up a layer
that may be a cause of failure.

3. If you not able to get rid of the linked tables, you can aim at creating
an Access query that pulls the data you desire and firing it off like a
stored procedure. I do not guarantee this will solve the problem, but it is
worth a try.

4. Another possible means of attack is putting the data access logic into a
component that uses COM+ and assigning a "super user" type account to the
application it runs in. NOTE: By application, I mean COM+ applications, which
used to be called packages under MTS. This will likely get you around
permission issues without having to reduce security on the machine.

Finally, a Q&A:

What version of Windows is the app on? If Windows 2003, the security model
is changed and may be an issue, esp. if the data directory(s) are outside of
the web hierarchy. This is a common issue.

What are the perms both on the Access directory and the DBase files? Unless
you have a layer that assumes an identity (COM+ comes to mind), the identity
of the web server carries all the way down to the files. This means you might
have access to certain raw files, but not others, causing a blow up. The user
account running to access the data (IUSR for anon access, or Network Service
in Windows 2003) must have access up and down the chain. If not ... BOOM!



--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************


[quoted text, click to view]