wrkgrp switch points to original system.mdw

[Guest]

Hi,
I created a new workgroup and shortcut.

"C:\Program files\Microsoft Office\Office10\MSACCESS.EXE"
"C:\TestRWOP\Original_Data.mdb"
/wrkgrp "C:\TestRWOP\LogAttempt.mdw"

I get the message "Original_Data.mdb" not found. I click Okay
Next Messaage "...can't find file Cocuments and Settings\Carla\Application
Data\Microsoft Access|System1.mdw"

The System.mdw was in Docments and Settings\etc file, but I copied and
renamed it to C:\TestRWOP to practice creating workgroup files.

Do tell, what was my blunder?

Thanks for everything.

Charlie

 

[Keith Wilby]

Hi,
I created a new workgroup and shortcut.

"C:\Program files\Microsoft Office\Office10\MSACCESS.EXE"
"C:\TestRWOP\Original_Data.mdb"
/wrkgrp "C:\TestRWOP\LogAttempt.mdw"

I get the message "Original_Data.mdb" not found. I click Okay
Next Messaage "...can't find file Cocuments and
Settings\Carla\Application
Data\Microsoft Access|System1.mdw"

The System.mdw was in Docments and Settings\etc file, but I copied and
renamed it to C:\TestRWOP to practice creating workgroup files.

Do tell, what was my blunder?

Thanks for everything.

Charlie

If the command line is right then check the contents of "start in".

Keith.

 

[Guest]

Keith, Thanks for your response.
It says Start In: C:\TestRWOP
Charlie

 

[Joan Wild]

I created a new workgroup and shortcut.

"C:\Program files\Microsoft Office\Office10\MSACCESS.EXE"
"C:\TestRWOP\Original_Data.mdb"
/wrkgrp "C:\TestRWOP\LogAttempt.mdw"

I get the message "Original_Data.mdb" not found. I click Okay
Next Messaage "...can't find file Cocuments and
Settings\Carla\Application Data\Microsoft Access|System1.mdw"

I'll assume that is a typo and should read
C:\Documents and Settings\Carla\Application Data\Microsoft
Access\System1.mdw
When it couldn't find Original_Data.mdb, all bets are off regarding the
workgroup file, so Access attempts to open using the default workgroup file,
which in your case is stored in that D and S folder.

The problem then is that it can't find c:\TestRWOP\Original_Data.mdb. Are
you certain that is the pathname? Maybe that underscore should be a space?

The System.mdw was in Docments and Settings\etc file, but I copied and
renamed it to C:\TestRWOP to practice creating workgroup files.

If you want to practice on workgroup files/setting up security, do *not*
start by copying system.mdw. You will never get a secure mdb. Step 1 is to
create a *new* mdw, and you do that using the workgroup administrator.

Backup your mdb. Then copy it. Then practice on this copy. You need to
follow a set of steps, in order. See
Security FAQ
http://support.microsoft.com/?id=207793

Security Whitepaper
http://support.microsoft.com/?id=148555

Although the whitepaper is old, it contains information to help you
understand security.

I've also outlined the detailed steps at
www.jmwild.com/AccessSecurity.htm

 

[Guest]

Hi Joan,
Thank you for your response. I did create a new workgroup file
LogAttempt.mdw. I didn't follow your document of security but did Jack
McDonald's when i was working in A2000 which is why I am practicing again for
a new secure database in A2003 - I wanted to practice those steps again with
a test database. Where my methods became crude and not following his paper
is copying the system.mdw and the old unsecure database for testing. I am
currently at the point in his paper for putting in the shortcut. Actually
securing the database by locking out the default Admin - is on the next page.

I am not sure of all the implications of my findings but I either found the
error or a work around. (I checked my paths and names, typos many, many
times. I am sure this was not the problem) I think it has something to do
with copying the database Original_data.mdb. Is it possible that
MSACCESS.EXE did not recognize a database that was copied from a different
computer?

This is why I think so and please feel free to correct me:

I opened Access and immediately joined my new workgroup. LogAttempt.mdw.
Then I created a new database TestAssumptions.mdb. I went to my shortcut
that previously was not working and typed in the new database name instead of
Original_data.mdb. This works. All mdw's and mdb's reside in the same
folder. The only that did not was the MSACCESS.EXE.

Thank you for your link to security fax. I will also check it out, also. I
really appreciate what you all do. I have seen your name many times in the
threads.

Charlie

 

[Joan Wild]

Hi Joan,
Thank you for your response. I did create a new workgroup file
LogAttempt.mdw. I didn't follow your document of security but did Jack
McDonald's when i was working in A2000 which is why I am practicing
again for a new secure database in A2003 - I wanted to practice those
steps again with a test database. Where my methods became crude and
not following his paper is copying the system.mdw and the old
unsecure database for testing.

I'm saying that you should NOT do this. Why are you copying system.mdw?
You need to create a new workgroup file, like you did before.

Is it possible that MSACCESS.EXE did not recognize a database that
was copied from a different computer?

No, unless it was created in a different version. But that would yield a
different error message.

This is why I think so and please feel free to correct me:

I opened Access and immediately joined my new workgroup.
LogAttempt.mdw. Then I created a new database TestAssumptions.mdb. I
went to my shortcut that previously was not working and typed in the
new database name instead of Original_data.mdb. This works. All
mdw's and mdb's reside in the same folder. The only that did not was
the MSACCESS.EXE.

Are you able to use this shortcut (to open TestAssumptions.mdb); and once
it's opened, then use Ctrl-O or File Open and open the Original_data.mdb
file?

 

[hireagenius via AccessMonster.com]

Hi Joan,
Thank you for your response. I did create a new workgroup file

[quoted text clipped - 4 lines]

not following his paper is copying the system.mdw and the old
unsecure database for testing.

I'm saying that you should NOT do this. Why are you copying system.mdw?
You need to create a new workgroup file, like you did before.

Is it possible that MSACCESS.EXE did not recognize a database that
was copied from a different computer?

No, unless it was created in a different version. But that would yield a
different error message.

This is why I think so and please feel free to correct me:

[quoted text clipped - 4 lines]

mdw's and mdb's reside in the same folder. The only that did not was
the MSACCESS.EXE.

Are you able to use this shortcut (to open TestAssumptions.mdb); and once
it's opened, then use Ctrl-O or File Open and open the Original_data.mdb
file?

Why yes, I can. Is that not a good thing? Anyway, Joan, I do not wish to
consume more of your time on this issue. Since it works, I am moving forward.
I really appreciate your help.---

 

[Joan Wild]

Why yes, I can. Is that not a good thing? Anyway, Joan, I do not
wish to consume more of your time on this issue. Since it works, I
am moving forward. I really appreciate your help.---

No that's OK, I was just trying to confirm that you can open the
Original_data.mdb. There must have been something incorrect in your
shortcut.

As long as you're back in the saddle, that's fine.