By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,659 Members | 1,939 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,659 IT Pros & Developers. It's quick & easy.

Upgrading Access 97 - DAO or dao. ?

Expert 100+
P: 446
Hi Guys

I'm finally converting some old Access 97 stuff to 2003 and as you know part of this procedure is to explicitly qualify Database, Recordset and TableDef objects as DAO.

When I have done this previously the 'autocorrect' feature changed lowercase 'dao.' to uppercase 'DAO.' but not today!

I have obviously checked that I have the right references (MS DAO 3.6 Object Library and MS VBA Extensibility 5.3) and even that they are in the same order in both systems. They are also both on the same laptop (XP) and they both compile ok.

I rely on the 'auto-correct' to rectify my atrocious typing so ame very concious when words do not 'capitalise' correctly.

Anybody any ideas?

Any other gottcha's in upgrading to watch for ?

Many thanks

S7
Jan 8 '08 #1
Share this Question
Share on Google+
7 Replies


puppydogbuddy
Expert 100+
P: 1,923
Hi Guys

I'm finally converting some old Access 97 stuff to 2003 and as you know part of this procedure is to explicitly qualify Database, Recordset and TableDef objects as DAO.

When I have done this previously the 'autocorrect' feature changed lowercase 'dao.' to uppercase 'DAO.' but not today!

I have obviously checked that I have the right references (MS DAO 3.6 Object Library and MS VBA Extensibility 5.3) and even that they are in the same order in both systems. They are also both on the same laptop (XP) and they both compile ok.

I rely on the 'auto-correct' to rectify my atrocious typing so ame very concious when words do not 'capitalise' correctly.

Anybody any ideas?

Any other gottcha's in upgrading to watch for ?

Many thanks

S7
Why can't you do a find and replace (for the project) using the VB editor code window?
Jan 8 '08 #2

Expert 100+
P: 446
Why can't you do a find and replace (for the project) using the VB editor code window?
Yes, of course I am doing that (149 replacements, times 3, sort of. I dont want to try and find all of those by hand!) But they should all turn into Upper case.

I'm probably worrying about nothing but a lot of money goes through this system (not mine I hasten to add!!) and I don't want any screw-ups.

Thanks for the suggestion anyway.
Jan 8 '08 #3

puppydogbuddy
Expert 100+
P: 1,923
Yes, of course I am doing that (149 replacements, times 3, sort of. I dont want to try and find all of those by hand!) But they should all turn into Upper case.

I'm probably worrying about nothing but a lot of money goes through this system (not mine I hasten to add!!) and I don't want any screw-ups.

Thanks for the suggestion anyway.

You can also try this free global find and replace utility for Access.

http://www3.bc.sympatico.ca/starthere/findandreplace/
Jan 8 '08 #4

jaxjagfan
Expert 100+
P: 254
Can you post some of the relevant code?

Make sure when you check "References" none are flagged as "Missing" if so uncheck these and try again. I have seen at times where these were not needed but were the cause of problems.
Jan 8 '08 #5

Expert 100+
P: 446
The Panic is over !!

When I opened the project this morning I found everything capitalised OK.
So declarations are now appearing correctly like;-
Expand|Select|Wrap|Line Numbers
  1. Dim dbs As DAO.Database
  2. Dim rst As DAO.Recordset
instead of like;-
Expand|Select|Wrap|Line Numbers
  1. Dim dbs As dao.Database
  2. Dim rst As dao.Recordset
I know I could have done a Find & Replace and forced capitals but that was not my point. I wanted the compiler to understand what I had written. I always type in lower case and wait for the capitals to appear. The Perfect Programmer may well look upon this practise as a lazy cop-out; so be it.

With hindsight, I had seen something similar before, when typing single statements e.g.
Expand|Select|Wrap|Line Numbers
  1. Me.Ndate_Label.Caption = !nextdate
  2. 'would not automatically capitalise to;
  3. Me.Ndate_Label.Caption = !NextDate
Thanks all for giving you time and PuppyDogBuddy thanks for the utility. I will try it later but if it can search Queries without opening them it will be good.

S7
Jan 9 '08 #6

puppydogbuddy
Expert 100+
P: 1,923
The Panic is over !!

When I opened the project this morning I found everything capitalised OK.
So declarations are now appearing correctly like;-
Expand|Select|Wrap|Line Numbers
  1. Dim dbs As DAO.Database
  2. Dim rst As DAO.Recordset
instead of like;-
Expand|Select|Wrap|Line Numbers
  1. Dim dbs As dao.Database
  2. Dim rst As dao.Recordset
I know I could have done a Find & Replace and forced capitals but that was not my point. I wanted the compiler to understand what I had written. I always type in lower case and wait for the capitals to appear. The Perfect Programmer may well look upon this practise as a lazy cop-out; so be it.

With hindsight, I had seen something similar before, when typing single statements e.g.
Expand|Select|Wrap|Line Numbers
  1. Me.Ndate_Label.Caption = !nextdate
  2. 'would not automatically capitalise to;
  3. Me.Ndate_Label.Caption = !NextDate
Thanks all for giving you time and PuppyDogBuddy thanks for the utility. I will try it later but if it can search Queries without opening them it will be good.

S7
sierra7,

Here is another good free utility that you should have:

http://www.mztools.com/v3/features.aspx
Jan 9 '08 #7

Expert 100+
P: 446
sierra7,

Here is another good free utility that you should have:

http://www.mztools.com/v3/features.aspx
WOW they look good but I am short of time today to experiment much.

I use mainly Access and have acquired the (lazy) habit of creating a suitably named phantom command button with the Wizard to give me a default error handling subroutine, then delete the button and remove the OnClick bits. These tools should be much better.

Thanks again
Jan 9 '08 #8

Post your reply

Sign in to post your reply or Sign up for a free account.