Name Autocorrect and FE copy

[accessuser via AccessMonster.com]

I read many previous posts regarding the Name AutoCorrect, but I am having a
hard time understanding it. When I first started creating the database, the
Name AutoCorrect was turned on by default, and right now my database is
almost completed. However, after reading those posts, I decided to turn off
my Name AutoCorrects. Will it affect what I did on my database? Upon
completing my database, i'll give each user a copy, will I still need to turn
off on all user copies later on?

Is it better for me to put the FE on the company's shared drive and have each
users copy and paste into their desktop or should I visit their office and
copy and paste it that way? If I ever decide to redesign my forms on my FE
copy; I'll have to ask all users delete the old ones and upload the new FE
into their desktop, is that correct?

If I change my MS Access Icon, when my users get my database copies, will
they have the new Icon or still the "Key" default icon from MS. I want my
users to have an unique Icon for my database file only but without affecting
the MS Access Software in their system. Can this be done, if so how? And
lastly, where can I get a free nice looking (other than the Key) icon.

Sorry for the lengthy questions. Thank you so much in advance.

 

[Allen Browne]

Lotsa questions. Answers in-line.

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

I read many previous posts regarding the Name AutoCorrect, but I am having
a
hard time understanding it. When I first started creating the database,
the
Name AutoCorrect was turned on by default, and right now my database is
almost completed. However, after reading those posts, I decided to turn
off
my Name AutoCorrects. Will it affect what I did on my database? Upon
completing my database, i'll give each user a copy, will I still need to
turn
off on all user copies later on?

Once you uncheck the Name AutoCorrupt boxes, and compact the database, the
file should be okay. It would probably be good practice to do a decompile
and compact again anyway.

(Naturally, if you were relying on this "feature" to recognise changed field
names in your forms, that won't work any more.)

This setting is per mdb file (not per user or per computer), so there is no
need to visit each computer to change this setting.

Is it better for me to put the FE on the company's shared drive and have
each
users copy and paste into their desktop or should I visit their office and
copy and paste it that way? If I ever decide to redesign my forms on my
FE
copy; I'll have to ask all users delete the old ones and upload the new FE
into their desktop, is that correct?

The ideal is for each user to have a local copy of the FE. The crucial
aspect is that every user muse open a different FE (not all in the same FE),
so if the network admin insists the FE must go into each user's workspace on
the server rather than their local hard disk, that will work, though the
admin should be aware it will be slower and increase network traffic.

Tony Toews has an FE updater utility if it helps:
http://www.granite.ab.ca/access/autofe.htm

If I change my MS Access Icon, when my users get my database copies, will
they have the new Icon or still the "Key" default icon from MS. I want my
users to have an unique Icon for my database file only but without
affecting
the MS Access Software in their system. Can this be done, if so how?
And
lastly, where can I get a free nice looking (other than the Key) icon.

You can use your initialization code to set the AppIcon path. This kind of
thing:

Currentdb.Properties("AppIcon") = CurrentProject.Path & "\MyFile.ico"
Application.RefreshTitleBar

(Note that the property does not exist if you never assigned an icon.)

 

[accessuser via AccessMonster.com]

Allen,

So, what's the difference between the following two:

1) Have one FE on the Shared Drive, have users go in to the shared drive
themselves, Copy the database and Paste into their own C drives or desktops.
(After they copy and paste into their own PC, they'll be using the one on
their PC instead of FE on the Shared Drive). That way they are not using the
same FE.


2) I'll go to their offices, go into the Shared Drive where I save my FE
database, Copy and Paste into their C drive.

Am I thinking it correctly?? Should I do it in option 1 or is it better for
me to visit them and still follow the same step, copy from shared drive and
paste into each individual pcs? does it make any difference to database??

Sorry, it is just little confusing and I want to make sure everything runs
smoothly when it go live.

Thanks for taking the time to reply!!!

Lotsa questions. Answers in-line.

I read many previous posts regarding the Name AutoCorrect, but I am having
a

[quoted text clipped - 7 lines]

turn
off on all user copies later on?

Once you uncheck the Name AutoCorrupt boxes, and compact the database, the
file should be okay. It would probably be good practice to do a decompile
and compact again anyway.

(Naturally, if you were relying on this "feature" to recognise changed field
names in your forms, that won't work any more.)

This setting is per mdb file (not per user or per computer), so there is no
need to visit each computer to change this setting.

Is it better for me to put the FE on the company's shared drive and have
each

[quoted text clipped - 3 lines]

copy; I'll have to ask all users delete the old ones and upload the new FE
into their desktop, is that correct?

The ideal is for each user to have a local copy of the FE. The crucial
aspect is that every user muse open a different FE (not all in the same FE),
so if the network admin insists the FE must go into each user's workspace on
the server rather than their local hard disk, that will work, though the
admin should be aware it will be slower and increase network traffic.

Tony Toews has an FE updater utility if it helps:
http://www.granite.ab.ca/access/autofe.htm

If I change my MS Access Icon, when my users get my database copies, will
they have the new Icon or still the "Key" default icon from MS. I want my

[quoted text clipped - 3 lines]

And
lastly, where can I get a free nice looking (other than the Key) icon.

You can use your initialization code to set the AppIcon path. This kind of
thing:

Currentdb.Properties("AppIcon") = CurrentProject.Path & "\MyFile.ico"
Application.RefreshTitleBar

(Note that the property does not exist if you never assigned an icon.)

 

[Allen Browne]

At a quick read, I don't see any difference between whether you go and copy
it to their local C: drive, or whether they do it themselves. Perhaps it
might depend on how savvy the users are?

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

Allen,

So, what's the difference between the following two:

1) Have one FE on the Shared Drive, have users go in to the shared drive
themselves, Copy the database and Paste into their own C drives or
desktops.
(After they copy and paste into their own PC, they'll be using the one on
their PC instead of FE on the Shared Drive). That way they are not using
the
same FE.


2) I'll go to their offices, go into the Shared Drive where I save my FE
database, Copy and Paste into their C drive.

Am I thinking it correctly?? Should I do it in option 1 or is it better
for
me to visit them and still follow the same step, copy from shared drive
and
paste into each individual pcs? does it make any difference to database??

Sorry, it is just little confusing and I want to make sure everything runs
smoothly when it go live.

Thanks for taking the time to reply!!!

Lotsa questions. Answers in-line.

I read many previous posts regarding the Name AutoCorrect, but I am
having
a

[quoted text clipped - 7 lines]

turn
off on all user copies later on?

Once you uncheck the Name AutoCorrupt boxes, and compact the database, the
file should be okay. It would probably be good practice to do a decompile
and compact again anyway.

(Naturally, if you were relying on this "feature" to recognise changed
field
names in your forms, that won't work any more.)

This setting is per mdb file (not per user or per computer), so there is
no
need to visit each computer to change this setting.

Is it better for me to put the FE on the company's shared drive and have
each

[quoted text clipped - 3 lines]

copy; I'll have to ask all users delete the old ones and upload the new
FE
into their desktop, is that correct?

The ideal is for each user to have a local copy of the FE. The crucial
aspect is that every user muse open a different FE (not all in the same
FE),
so if the network admin insists the FE must go into each user's workspace
on
the server rather than their local hard disk, that will work, though the
admin should be aware it will be slower and increase network traffic.

Tony Toews has an FE updater utility if it helps:
http://www.granite.ab.ca/access/autofe.htm

If I change my MS Access Icon, when my users get my database copies,
will
they have the new Icon or still the "Key" default icon from MS. I want
my

[quoted text clipped - 3 lines]

And
lastly, where can I get a free nice looking (other than the Key) icon.

You can use your initialization code to set the AppIcon path. This kind of
thing:

Currentdb.Properties("AppIcon") = CurrentProject.Path & "\MyFile.ico"
Application.RefreshTitleBar

(Note that the property does not exist if you never assigned an icon.)

 

[accessuser via AccessMonster.com]

Thanks for the reply. I know what I am going to do now. While on this topic,
I would like to ask you again if it will make any difference on password
changes. Currently, I have a frmpassword for each dept (13 depts), and I
used the VBA codes for the password like <password>. In the future, if the
users want to change their password, they will have to contact me, and then I
change the password on my FE copy in VBA codes, will the code carries over or
will I need to give users a new copy?

I'd read something like Login table and login form, but I can't find it now.
As for login that base on a table, will I be able to limit the dept they can
go in? I don't like to use the user-level security because it is so
complicated and almost lost my database for few times.

Sorry for so many questions.

Thanks again!

At a quick read, I don't see any difference between whether you go and copy
it to their local C: drive, or whether they do it themselves. Perhaps it
might depend on how savvy the users are?

Allen,

[quoted text clipped - 76 lines]

 

[Allen Browne]

If you are using Access security, the MDW file usually resides in the same
folder as the back end, so everyone can access it. A change in a user's
password is just a matter of them supplying the correct password on startup.
But if you change the path to the back end, they will need adequate
priviliges before they can reconnect (i.e. they may not have the permissions
to reassing the Connect property of the TableDefs.) You could find out more
by asking in the group microsoft.public.access.security.

If you are rolling your own security using your own form and passwords, it
depends entirely on your code, so I can't comment.

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

Thanks for the reply. I know what I am going to do now. While on this
topic,
I would like to ask you again if it will make any difference on password
changes. Currently, I have a frmpassword for each dept (13 depts), and I
used the VBA codes for the password like <password>. In the future, if
the
users want to change their password, they will have to contact me, and
then I
change the password on my FE copy in VBA codes, will the code carries over
or
will I need to give users a new copy?

I'd read something like Login table and login form, but I can't find it
now.
As for login that base on a table, will I be able to limit the dept they
can
go in? I don't like to use the user-level security because it is so
complicated and almost lost my database for few times.

Sorry for so many questions.

Thanks again!

At a quick read, I don't see any difference between whether you go and
copy
it to their local C: drive, or whether they do it themselves. Perhaps it
might depend on how savvy the users are?

Allen,

[quoted text clipped - 76 lines]

(Note that the property does not exist if you never assigned an icon.)