Answers embedded.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Reply to group, rather than allenbrowne at mvps dot org.
DD said:
Our company uses access 2003 through citrix. i have written alot of
databases in access 97 and need to start converting to 2003. what is the
best way to do this. I have my databases split currently. if I try to
convert as is, does the back end get converted? will only 2003 users then
get to use the database
When you convert a database, only the mdb you specify is converted. So, if
you convert the front end, the back end is still an A97 mdb. A2003 can
connect to an A97 back end without difficulty, so you can now have some
users with an A97 front end and some users with an A2003 front end
simultaneously connecting to the A97 back end.
If you do retain the A97 front end, I suggest you set it not to use record
level locking under:
Tools | Options | Advanced
Of course the A97 back end does not support record-level locking, but my
experience is that some DAO transactions will fail to complete until you
disable this setting.
Once you have all users on A2003, I suggest you then convert the back end
mdb to A2003 also. The performance difference is noticeable, since the JET 4
calls are not having to be constantly converted internally to JET 3.5 calls
to execute against the A97 back end.
There's a bunch of other performance issues you need to be aware of as well.
Tony Toews has a list here:
http://www.granite.ab.ca/access/performancefaq.htm
also my security is controlled by forms. I currently have this control
listed on the main form that opens when the DB is started. current
user=environ$("username") then I use an if statement on "current" of the
form to display what controls are enabled for each user. I use 2003 to
open the database and it converts fine with a few warning messages coming
up. the current user control works fine. but then I open it again and it
displays an error message and a #name is displayed in this control. I
cant figure out why. am I not converting it properly. any help would be
appreciated.
These "warning messages" -- do they come up every time you start A2003?
There are some security messages that are a real pain. For info on how to
dump them, and a bunch of other info on bugs and issues, see:
Converting from Access 97
at:
http://allenbrowne.com/ser-48.html
If the "warning messages" were actually during the conversion process and
not those security messages, it might be important to read them. They might
indicate a corruption, an incomplete conversion, reference problems, or
something else. For help on references for each version, see:
http://allenbrowne.com/ser-38.html
Environ("username") should be fine. If you want an alternative approach (API
call), see:
http://www.mvps.org/access/api/api0008.htm
The #Name that works the first time but not again later could be related to
several issues. If there are other calculated controls on your form, it
could be triggered by one of those. As you probably realize, one Access is
unable to assign a value to a calculated control it gives up, and so other
calculated control error out also.
If you have not disabled the Name AutoCorrect problem options under:
Tools | Options | General
they could also contribute to Access's confusion here. More info:
Failures caused by Name Auto-Correct
at:
http://allenbrowne.com/bug-03.html
Presumably you have applied SP2 for Office 2003. An older version of JET
does cause this problem also. The service packs can be linked here:
http://support.microsoft.com/gp/sp
If none of those apply to your #name issue, double-check that the Name of
this text box is not the same as the name of any field in the form's
recordsource, any properties of the form, or any VBA reserved words or
public methods. There is a list of bad names in this utility:
http://allenbrowne.com/AppIssueChecker.html
If you're still stuck after that, post more info about what is in the
Control Source of this text box, and any other calculated controls on the
form.
HTH.
