Win2000 does not recognizing shortcut paths

[Jan Il]

Hi all! Win 2K, Access 2002 XP

I am new to your newsgroup, as I have just recently installed Win2000 on a
new hard drive on my machine along with WinME on the old hard drive. Right
now I'm dual booting until I have a chance to get all the stuff setup and
transferred over from ME to W2k.

One of the problems that I have encountered at the immediate moment, is that
when I have transferred my data files to the new W2K hard drive, put the in
the proper path folders, and then created a new shortcut to an existing
database on the new hard drive, I am getting the following error message:

Cannot find the file ""C:\Documents and Settings\jan\My
Documents\Access\Jan's Checking Registry\Jan's Checking.mdb"

The path in the shortcut is as follows:

"C:\Documents and Settings\jan\My Documents\Access\Jan's Checking
Registry\Jan's Checking.mdb"....which is the correct location of the file. I
even did a manual Find Target, and right clicked the file and did a Create
Shortcut, and it still gives me this error. But, it goes on to open the
file ok.

Although it opens the file, I tarry to ignore the problem, as I am not sure
at what point I may wind up with a corrupted file. While I have everything
backed up twice, I don't like having such situations going on.

I would truly appreciate any suggestions, as I am not sure if this is a W2K
related issue, or one for the Access ng, although, it does not involve any
database activities.

Jan
Smiles are meant to be shared,
that's why they're so contagious.

 

[Pegasus \(MVP\)]

Hi all! Win 2K, Access 2002 XP

I am new to your newsgroup, as I have just recently installed Win2000 on a
new hard drive on my machine along with WinME on the old hard drive. Right
now I'm dual booting until I have a chance to get all the stuff setup and
transferred over from ME to W2k.

One of the problems that I have encountered at the immediate moment, is that
when I have transferred my data files to the new W2K hard drive, put the in
the proper path folders, and then created a new shortcut to an existing
database on the new hard drive, I am getting the following error message:

Cannot find the file ""C:\Documents and Settings\jan\My
Documents\Access\Jan's Checking Registry\Jan's Checking.mdb"

The path in the shortcut is as follows:

"C:\Documents and Settings\jan\My Documents\Access\Jan's Checking
Registry\Jan's Checking.mdb"....which is the correct location of the file. I
even did a manual Find Target, and right clicked the file and did a Create
Shortcut, and it still gives me this error. But, it goes on to open the
file ok.

Although it opens the file, I tarry to ignore the problem, as I am not sure
at what point I may wind up with a corrupted file. While I have everything
backed up twice, I don't like having such situations going on.

I would truly appreciate any suggestions, as I am not sure if this is a W2K
related issue, or one for the Access ng, although, it does not involve any
database activities.

Jan
Smiles are meant to be shared,
that's why they're so contagious.

I note two double quotes after the word "file" in your post
where there should be one only:

 

[Jan Il]

Hi Pegasus

I note two double quotes after the word "file" in your post
where there should be one only:

I'm afraid that is a typo on my part when typing in the message, but, I have
created several new shortcuts from the target file, and copied to my
desktop, and I still get this error message before it opens the file. It is
only happening with the shortcuts, and only the Access shortcuts, as Word,
Excel and PowerPoint shortcuts all work fine. Also, if I open the Access
files from within a new Access event, I don't not get any error message, it
opens fine. I am puzzled as to why this is happening with the shortcuts.
It is not an Access file problem, otherwise, I'd get the same error message
when I open the file from within a new Access event. Thus, I suspect that
there is something in the setup with 2000 somehow that is not it is not
liking with these shortcuts.

Thank you very much for your time and assistance, I truly appreciate it.

Jan
Smiles are meant to be shared,
that's why they're so contagious.

 

[Pegasus \(MVP\)]

Hi Pegasus

I'm afraid that is a typo on my part when typing in the message, but, I have
created several new shortcuts from the target file, and copied to my
desktop, and I still get this error message before it opens the file. It is
only happening with the shortcuts, and only the Access shortcuts, as Word,
Excel and PowerPoint shortcuts all work fine. Also, if I open the Access
files from within a new Access event, I don't not get any error message, it
opens fine. I am puzzled as to why this is happening with the shortcuts.
It is not an Access file problem, otherwise, I'd get the same error message
when I open the file from within a new Access event. Thus, I suspect that
there is something in the setup with 2000 somehow that is not it is not
liking with these shortcuts.

Thank you very much for your time and assistance, I truly appreciate it.

Jan
Smiles are meant to be shared,
that's why they're so contagious.

Run the following experiments in order to home in on the problem:

1. Create a shortcut on your desktop for MS Access. The target
is probably "c:\Program Files\Microsoft Office\Office\msaccess.exe".

2. Double-click this shortcut. Does it work?

3. Create a sample database "c:\Test.mdb".

4. Place the database name into the target box of the new shortcut like so:
"c:\Program Files\Microsoft Office\Office\msaccess.exe" "c:\Test.mdb"

5. Double-click this shortcut. Does it work?

6. Create a new shortcut. Put just "c:\Test.mdb" into the target box.

7. Double-click this shortcut. Does it work?

8. Modify the shortcut created under 1 by putting this into the target box:
"c:\Program Files\Microsoft Office\Office\msaccess.exe" "C:\Documents
and Settings\jan\My Documents\Access\Jan's Checking Registry\Jan's
Checking.mdb"
(This is one single long line!)
Does it work?

 

[Jan Il]

Hi Pegasus

I'll perform the tests and report back.

Thank you very much for your time and patience.

Jan
Smiles are meant to be shared,
that's why they're so contagious.

 

[Jan Il]

Hi Pegasus

Thank you very much for the infomation. I have tried the tests you provided
and found that this one did not work:

6. Create a new shortcut. Put just "c:\Test.mdb" into the target box.

However, this one did:

4. Place the database name into the target box of the new shortcut like so:
"c:\Program Files\Microsoft Office\Office\msaccess.exe" "c:\Test.mdb

It opened the db without the error. Thus, I copied and pasted the
"C:\Program Files\Microsoft Office\Office\msaccess.exe" in front of the
"C:\Documents and Settings\jan\My Documents\Access\Jan's Checking
Registry\Jan's Checking.mdb" in the original shortcut, and it opened the db
without any errors.

It does still show the dialog box that it is configuring the Office 2002 XP
Professional (again)and goes through the process before opening the db, but,
at least I'm not getting any errors any more.

What is the factor of the additional path in this case? I have done that
with secure db's, but, I have never had to do that with an unsecured db
shortcut.

Thank you very much for you time and help, I really do appreciate it.

Jan
Smiles are meant to be shared,
that's why they're so contagious.

 

[Pegasus \(MVP\)]

The proper way to open a file goes line this:

"SomePath\ApplicationName.exe" "SomeOtherPath\DataFile.ext"

By way of "associations", Windows allows you to specify just the
data file in the target box of a shortcut". As an example, .txt files
are usually associated with "%SystemRoot%\system32\notepad.exe".
However, one should not rely on these shortcuts; they are nowhere
near as robust as the standard method.

Your report indicates that your association for .mdb files is
incorrect. You can check it with asscociate.exe (Win2000
Resource Kit) or in Explorer.

 

[Jan Il]

Hi Pegasus

The proper way to open a file goes line this:

"SomePath\ApplicationName.exe" "SomeOtherPath\DataFile.ext"

By way of "associations", Windows allows you to specify just the
data file in the target box of a shortcut". As an example, .txt files
are usually associated with "%SystemRoot%\system32\notepad.exe".
However, one should not rely on these shortcuts; they are nowhere
near as robust as the standard method.

Your report indicates that your association for .mdb files is
incorrect. You can check it with asscociate.exe (Win2000
Resource Kit) or in Explorer.

In persuing this issue further, I found what I believe was the main cause of
the problem.

Here is what I did:

I uninstalled the Office 2002XP and then rebooted to make sure all was
clear. Then I reinstalled it by doing the following:

Placed the 2002 XP install CD in the E:\ CD-Rom drive and started the
install process. When it asked for the qualifying program, I removed the
2002 XP CD and put in the 2000 CD and set the drive source to the E:\ drive.
Once it went to the 'Accept' window, I took the 2000 CD out and put the 2002
XP CD back in the E:\ drive and then had it finish the install process. Then
I rebooted to make sure all the ingredients were well blended.

Well....guess what?!?!? Yeppers! The main MS Access program desktop
shortcut opens with no dialog box about installing and configuring the 2002
XP.....AND.....I tried creating new shortcuts by just right clicking the
file and then selecting Create shortcut, and putting them on the desktop,
and....they now open the respective db's without the error message, and I
don't need the "C:\Program Files\Microsoft Office\Office10\MSACCESS.EXE"!

Heh! Whadda ya know.... it worked!!

I'm not sure what the difference is in putting the qualifying CD in the same
ROM drive as the install CD, then removing it and putting the install CD
back in, but, in this instance at least, it did resolve the problem on all
fronts. I guess this is another part of the program I'm learning about.
While my 'lil one cell boggles with all the new stuff and such to learn, the
adventure is truly so much fun!!! ;-))

Thank you again for all your help and the additional information. I really
appreciate it. I've added the information here to my resources library for
future reference.

Jan
Smiles are meant to be shared,
that's why they're so contagious.