Pathing issue

  • Thread starter Thread starter Alex
  • Start date Start date
A

Alex

Hi, I have just taken over a database that was very heavily secured. i seem
to have got round all issues appart from when I start to load the database
and autoexec the main form, I am getting a C;\bios\systemsettings is not a
valid path.. error message.

I am assuming that this is set somewhere in one of the modules. Is there
anyway of doing a global search for this?

thanks

Alex
 
Hi, Alex.

Most likely this error message is from a linked table stored in a database
which is not located in the "C:\bios\systemsettings" directory on your
computer, but it could also be from another source, too, as you suspect.

First, check whether there are any linked tables listed in the database
window (the linked tables will have an arrow pointing to the icon for the
table if it's linked). If you don't have linked tables, then skip these
next steps. If you have linked tables, then use the Linked Table Manager to
find and relink the tables, if necessary. To do so in Access 2K and later
versions, select the Tools menu -> Database Utililtes -> Linked Table
Manager to open the Linked Table Manager dialog window. IIRC in Access 97,
select the Tools menu -> Add-ins -> Linked Table Manager to open the Linked
Table Manager dialog window. You'll see a list of tables and their paths.
If you see any with "C:\bios\systemsettings" then you'll need to change the
path for these tables to the location where the tables are now stored.

If it's not the linked tables causing the problem, then open any module in
the VB Editor and search "Current Project" for every occurance of the string
"C:\bios\systemsettings" and replace it with the correct path.

If you still can't find where the "C:\bios\systemsettings" string is, then
use the Documentor to create a report of all objects in the database, except
tables and modules, then export this report to an Excel spreadsheet and
search for every occurance of string "C:\bios\systemsettings" to determine
which property in which object is using this string, then go back to your
Access database application and change the appropriate property setting to
use the correct path.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
Thanks Gunny, that sorted it

'69 Camaro said:
Hi, Alex.

Most likely this error message is from a linked table stored in a database
which is not located in the "C:\bios\systemsettings" directory on your
computer, but it could also be from another source, too, as you suspect.

First, check whether there are any linked tables listed in the database
window (the linked tables will have an arrow pointing to the icon for the
table if it's linked). If you don't have linked tables, then skip these
next steps. If you have linked tables, then use the Linked Table Manager to
find and relink the tables, if necessary. To do so in Access 2K and later
versions, select the Tools menu -> Database Utililtes -> Linked Table
Manager to open the Linked Table Manager dialog window. IIRC in Access 97,
select the Tools menu -> Add-ins -> Linked Table Manager to open the Linked
Table Manager dialog window. You'll see a list of tables and their paths.
If you see any with "C:\bios\systemsettings" then you'll need to change the
path for these tables to the location where the tables are now stored.

If it's not the linked tables causing the problem, then open any module in
the VB Editor and search "Current Project" for every occurance of the string
"C:\bios\systemsettings" and replace it with the correct path.

If you still can't find where the "C:\bios\systemsettings" string is, then
use the Documentor to create a report of all objects in the database, except
tables and modules, then export this report to an Excel spreadsheet and
search for every occurance of string "C:\bios\systemsettings" to determine
which property in which object is using this string, then go back to your
Access database application and change the appropriate property setting to
use the correct path.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
Back
Top