Strange ASP MS Access Problem

Hi,
I have in my possession a large web application which I would like to
port to another machine, the application will be set up with the same
directory structure for the application but the databases connecting to
the applications will reside in different directories.

Now the problem is when all the connection strings are changed to
reflect the new paths for the databases there is one error that always
appears, the application cannot find the database
d:\somedire\somedir\somedatabase.mdb.

All the connection strings are properly changed, and searching through
all the files there are no connections strings that have to be changed.

When searching the databases the connection string is found in one of
the databases. How do I remove this embedded path from this database.

I have recreated a new database with the collection of 4 databases in
one and all the imported links from the 4 tables have been removed, with
the same results can't find database ....... .

Any Ideas on a solution would be appreciated.

Thanks
Jack Wayne

Re: Strange ASP MS Access Problem

Show the actual error message.
Show the code where the error is taking place.
Show the connection string in use by the line where the error occurs.

--
Mark Schupp
Head of Development
Integrity eLearning
www.ielearning.com


"Jack Wayne" wrote in message
news:418FF34F.42688EFD@yahoo.com...
> Hi,
> I have in my possession a large web application which I would like to
> port to another machine, the application will be set up with the same
> directory structure for the application but the databases connecting to
> the applications will reside in different directories.
>
> Now the problem is when all the connection strings are changed to
> reflect the new paths for the databases there is one error that always
> appears, the application cannot find the database
> d:\somedire\somedir\somedatabase.mdb.
>
> All the connection strings are properly changed, and searching through
> all the files there are no connections strings that have to be changed.
>
> When searching the databases the connection string is found in one of
> the databases. How do I remove this embedded path from this database.
>
> I have recreated a new database with the collection of 4 databases in
> one and all the imported links from the 4 tables have been removed, with
> the same results can't find database ....... .
>
> Any Ideas on a solution would be appreciated.
>
> Thanks
> Jack Wayne
>
>

Re: Strange ASP MS Access Problem

strSource = "PROVIDER = MICROSOFT.JET.OLEDB.4.0; DATA SOURCE
=C:\webpub\mysitename\database\mydb.mdb"

Microsoft JET Database Engine error '80004005'

'C:\webpub\mysitename\database\mydb.mdb' is not a valid path. Make sure that
the path name is spelled correctly and that you are connected to the server on
which the file resides.

/mysitename/somefile.asp, line 382

Line 382 is right in the middle of a function call.
The connection strings are correct as the rest of the application works
correctly, except for this one line that is referencing the old location of
the database.

Mark Schupp wrote:

> Show the actual error message.
> Show the code where the error is taking place.
> Show the connection string in use by the line where the error occurs.
>
> --
> Mark Schupp
> Head of Development
> Integrity eLearning
> www.ielearning.com
>
> "Jack Wayne" wrote in message
> news:418FF34F.42688EFD@yahoo.com...
> > Hi,
> > I have in my possession a large web application which I would like to
> > port to another machine, the application will be set up with the same
> > directory structure for the application but the databases connecting to
> > the applications will reside in different directories.
> >
> > Now the problem is when all the connection strings are changed to
> > reflect the new paths for the databases there is one error that always
> > appears, the application cannot find the database
> > d:\somedire\somedir\somedatabase.mdb.
> >
> > All the connection strings are properly changed, and searching through
> > all the files there are no connections strings that have to be changed.
> >
> > When searching the databases the connection string is found in one of
> > the databases. How do I remove this embedded path from this database.
> >
> > I have recreated a new database with the collection of 4 databases in
> > one and all the imported links from the 4 tables have been removed, with
> > the same results can't find database ....... .
> >
> > Any Ideas on a solution would be appreciated.
> >
> > Thanks
> > Jack Wayne
> >
> >

Re: Strange ASP MS Access Problem

Jack Wayne wrote:
> strSource = "PROVIDER = MICROSOFT.JET.OLEDB.4.0; DATA SOURCE
> =C:\webpub\mysitename\database\mydb.mdb"
>
> Microsoft JET Database Engine error '80004005'
>
> 'C:\webpub\mysitename\database\mydb.mdb' is not a valid path. Make
> sure that the path name is spelled correctly and that you are
> connected to the server on which the file resides.
>
> /mysitename/somefile.asp, line 382
>
> Line 382 is right in the middle of a function call.

That really does not help ...

> The connection strings are correct as the rest of the application
> works correctly, except for this one line that is referencing the old
> location of the database.
>
I don't understand. Why don't you change the strSource to reference the new
location of the database?

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"

Re: Strange ASP MS Access Problem

"Bob Barrows [MVP]" wrote in message news:<#zmWdnxxEHA.3120@TK2MSFTNGP12.phx.gbl>...
> Jack Wayne wrote:
> > strSource = "PROVIDER = MICROSOFT.JET.OLEDB.4.0; DATA SOURCE
> > =C:\webpub\mysitename\database\mydb.mdb"
> >
> > Microsoft JET Database Engine error '80004005'
> >
> > 'C:\webpub\mysitename\database\mydb.mdb' is not a valid path. Make
> > sure that the path name is spelled correctly and that you are
> > connected to the server on which the file resides.
> >
> > /mysitename/somefile.asp, line 382
> >
> > Line 382 is right in the middle of a function call.
>
> That really does not help ...

I understand this is not much help but this function but there is
nothing in the function that would generate this type of error.


>
> > The connection strings are correct as the rest of the application
> > works correctly, except for this one line that is referencing the old
> > location of the database.
> >
> I don't understand. Why don't you change the strSource to reference the new
> location of the database?

strSource references the proper location
C:\webpub\mysitename\database\mydb.mdb as example and notice the error
above
'C:\webpub\mysitename\database\mydb.mdb' is not a valid path. ....

All the connection string have been modified to reference the new
location. I have checked and rechecked all connection strings as well
as others, the ones who are thying to use the app.

If the paths of the connection strings remain the same there is not a
problem, but they cannot keep the path the same due to inadequate
access to the server.

I think this may be a path that is hidden somewhere in the databases
but not in any of the data, somewhere else in the .mdb file, is this
possible.

I am at a loss of where this connection string is coming from.

I have even combined all the databases together and changed all the
connection strings again to reference the one connection, with the
same resolution.

We have reinstalled the application, in the case of file corruption
again with no resolution.

Jack Wayne



>
> Bob Barrows

Re: Strange ASP MS Access Problem

Jack Wayne wrote:
> "Bob Barrows [MVP]" wrote in message
> news:<#zmWdnxxEHA.3120@TK2MSFTNGP12.phx.gbl>...
>> Jack Wayne wrote:
>>> strSource = "PROVIDER = MICROSOFT.JET.OLEDB.4.0; DATA SOURCE
>>> =C:\webpub\mysitename\database\mydb.mdb"
>>>
>>> Microsoft JET Database Engine error '80004005'
>>>
>>> 'C:\webpub\mysitename\database\mydb.mdb' is not a valid path. Make
>>> sure that the path name is spelled correctly and that you are
>>> connected to the server on which the file resides.
>>>
>>> /mysitename/somefile.asp, line 382
>>>
>>> Line 382 is right in the middle of a function call.
>>
>> That really does not help ...
>
> I understand this is not much help but this function but there is
> nothing in the function that would generate this type of error.

:-) Yes, there is.

>
>
>>
>>> The connection strings are correct as the rest of the application
>>> works correctly, except for this one line that is referencing the
>>> old
>>> location of the database.
>>>
>> I don't understand. Why don't you change the strSource to reference
>> the new
>> location of the database?
>
> strSource references the proper location
> C:\webpub\mysitename\database\mydb.mdb as example and notice the error
> above
> 'C:\webpub\mysitename\database\mydb.mdb' is not a valid path. ....

I'm not looking over your shoulder. Is
'C:\webpub\mysitename\database\mydb.mdb' a valid path or isn't it? You said
above that the error message referenced the old location of the database.
Now you're saying .... what? That strSource contains the correct path, but
the error message indicates a different path is being used?


> All the connection string have been modified to reference the new
> location. I have checked and rechecked all connection strings as well
> as others, the ones who are thying to use the app.
>
> If the paths of the connection strings remain the same there is not a
> problem, but they cannot keep the path the same due to inadequate
> access to the server.
>
> I think this may be a path that is hidden somewhere in the databases
> but not in any of the data, somewhere else in the .mdb file, is this
> possible.
>
Look for linked tables and passthrough queries in the database being used by
your asp application. They can easily be found by looking at the objects in
your database window in Access. The icons clearly indicate which objects
reference another database.

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"

Re: Strange ASP MS Access Problem

On 14 Nov 2004 17:56:54 -0800, herders@yahoo.com (Jack Wayne) wrote:

>"Bob Barrows [MVP]" wrote in message news:<#zmWdnxxEHA.3120@TK2MSFTNGP12.phx.gbl>...
>> Jack Wayne wrote:
>> > strSource = "PROVIDER = MICROSOFT.JET.OLEDB.4.0; DATA SOURCE
>> > =C:\webpub\mysitename\database\mydb.mdb"
>> >
>> > Microsoft JET Database Engine error '80004005'
>> >
>> > 'C:\webpub\mysitename\database\mydb.mdb' is not a valid path. Make
>> > sure that the path name is spelled correctly and that you are
>> > connected to the server on which the file resides.
>> >
>> > /mysitename/somefile.asp, line 382
>> >
>> > Line 382 is right in the middle of a function call.
>>
>> That really does not help ...
>
>I understand this is not much help but this function but there is
>nothing in the function that would generate this type of error.

Something passed to the function may be generating it. Have you
looked at the actual path versus what is being used?

>> > The connection strings are correct as the rest of the application
>> > works correctly, except for this one line that is referencing the old
>> > location of the database.
>> >
>> I don't understand. Why don't you change the strSource to reference the new
>> location of the database?
>
>strSource references the proper location
>C:\webpub\mysitename\database\mydb.mdb as example and notice the error
>above
> 'C:\webpub\mysitename\database\mydb.mdb' is not a valid path. ....

Have you checked for access to the location for the account using the
page? This may be a user account or it may be the anonymous user
account.

>All the connection string have been modified to reference the new
>location. I have checked and rechecked all connection strings as well
>as others, the ones who are thying to use the app.
>
>If the paths of the connection strings remain the same there is not a
>problem, but they cannot keep the path the same due to inadequate
>access to the server.
>
>I think this may be a path that is hidden somewhere in the databases
>but not in any of the data, somewhere else in the .mdb file, is this
>possible.

Not really as part of the MDB somewhere. If you had macros, or were
using saved queries then maybe the saved query is wrong, check and
see.

>I am at a loss of where this connection string is coming from.
>
>I have even combined all the databases together and changed all the
>connection strings again to reference the one connection, with the
>same resolution.
>
>We have reinstalled the application, in the case of file corruption
>again with no resolution.

That's a lot of moving and reinstalling, are you sure you didn't
introduce new errors? You say this is in a function, you need to find
what is calling the function and debug that. Use liberal
Response.Writes of your variables being passed to the function.

Jeff

Re: Strange ASP MS Access Problem

Jeff Cochran wrote:

> On 14 Nov 2004 17:56:54 -0800, herders@yahoo.com (Jack Wayne) wrote:
>
> >"Bob Barrows [MVP]" wrote in message news:<#zmWdnxxEHA.3120@TK2MSFTNGP12.phx.gbl>...
> >> Jack Wayne wrote:
> >> > strSource = "PROVIDER = MICROSOFT.JET.OLEDB.4.0; DATA SOURCE
> >> > =C:\webpub\mysitename\database\mydb.mdb"
> >> >
> >> > Microsoft JET Database Engine error '80004005'
> >> >
> >> > 'C:\webpub\mysitename\database\mydb.mdb' is not a valid path. Make
> >> > sure that the path name is spelled correctly and that you are
> >> > connected to the server on which the file resides.
> >> >
> >> > /mysitename/somefile.asp, line 382
> >> >
> >> > Line 382 is right in the middle of a function call.
> >>
> >> That really does not help ...
> >
> >I understand this is not much help but this function but there is
> >nothing in the function that would generate this type of error.
>
> Something passed to the function may be generating it. Have you
> looked at the actual path versus what is being used?

The path are all changed there are paths which are dynamically generated and some which are explicitly stated. they
have all been changed.
There are many connection strings in this app, some duplicated in many diffrent files.

>
> >> > The connection strings are correct as the rest of the application
> >> > works correctly, except for this one line that is referencing the old
> >> > location of the database.
> >> >
> >> I don't understand. Why don't you change the strSource to reference the new
> >> location of the database?
> >
> >strSource references the proper location
> >C:\webpub\mysitename\database\mydb.mdb as example and notice the error
> >above

my mistake, the following path should have been the old path

>
> > 'C:\webpub\mysitename\database\mydb.mdb' is not a valid path. ....
>
> Have you checked for access to the location for the account using the
> page? This may be a user account or it may be the anonymous user
> account.

I am pretty sure the anonymous user is the right user, but I will confirm that.
the databases are now in the wwwroot so I don't think there is an issue there.
Security issue yes but out of my control.

>
>
> >All the connection string have been modified to reference the new
> >location. I have checked and rechecked all connection strings as well
> >as others, the ones who are thying to use the app.
> >
> >If the paths of the connection strings remain the same there is not a
> >problem, but they cannot keep the path the same due to inadequate
> >access to the server.
> >
> >I think this may be a path that is hidden somewhere in the databases
> >but not in any of the data, somewhere else in the .mdb file, is this
> >possible.
>
> Not really as part of the MDB somewhere. If you had macros, or were
> using saved queries then maybe the saved query is wrong, check and
> see.

There are some saved queries never considered looking there. I will check. Any macros. not sure don't think so.

>
>
> >I am at a loss of where this connection string is coming from.
> >
> >I have even combined all the databases together and changed all the
> >connection strings again to reference the one connection, with the
> >same resolution.
> >
> >We have reinstalled the application, in the case of file corruption
> >again with no resolution.
>
> That's a lot of moving and reinstalling, are you sure you didn't
> introduce new errors?

No, I'm working on adding some new features to the application, the problem is this app is so poorly written and I
do not have the time to fix all the problems. Looking to get over this little hurdle with the connection strings.

> You say this is in a function, you need to find
> what is calling the function and debug that. Use liberal
> Response.Writes of your variables being passed to the function.

After transfering all the table to one database the same error occurred.
I have moved the appication in it's entirety to another development machine and it works fine, just in this case
there is a this strange association to the original connections string.

With reference to the previous post: the 4 databases are all linked together in one database with link table access.

Because of this I removed all imported link access of the other database tables, and transfered all the tables into
one database.

Thanks for the ideas a few things not considered
Jack Wayne

> Jeff