I have found a work around for this issue. The reason for a split DB was due to the linked tables being Visual Fox Pro tables. It looks like the linked tables just won't work for web apps properly. So, down loaded the latest oledb data provider for VFP and went to them directly.
"Amy Blankenship" wrote:
[Quoted Text] > I see you posted a while back. Did you ever get any help? > > First, why are you using a split database as the data source for a web > application? Second, are you saying that your web server is a machine that > you have physical access or other direct access such as PC Anywhere to? If > not, what you see when you open your GUI on your own machine is not what the > server will see. > > If you still need help, post back. > > > "Risk Factor" <RiskFactor[ at ]discussions.microsoft.com> wrote in message > news:39DAB94D-08C6-4300-B292-07A0DB47D4CC[ at ]microsoft.com... > >I have an mdb file in the root of my web app. There are several linked > > tables that I am trying to run a query against through my web app. My > > query > > succeeds and it those an exception that the path to the linked table is > > not > > valid. > > > > Here's the kicker. When I open the Access GUI I can open the linked > > tables > > and run the needed query without issue. > > > > The linked tables reside on the same server as my web app and the ASP.NET > > user account have permissions on both the web app root folder where the > > mdb > > sits and the folder where the linked tables reside. Seems to me that this > > might be an Access problem but I'm not 100% sure. Any thoughts? > > >
|