In Access 2003 VB code, control names resetting to upper case

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm trying to correct a compatibility issue by changing the table and field
names to all lowercase. In VB code, the control names automatically change
back to initial caps when I try to correct them.

For example, I enter:

Me!authornotes

As soon as I take the cursor off it, it reverts to:

Me!AuthorNotes

I've searched for hours trying to stop this--any assistance greatly
appreciated.
 
You've probably got it as AuthorName somewhere still, and that's affecting
all of the references. However, VB code is case insensitive, so it really
shouldn't matter.
 
Thanks Douglas,

I've done a major purge of tables, forms and code; the only thing I can
think of is wherever the Object Browser gets its Members list from. If I
select the [author] Form in the Classes column, I see AuthorNotes in the
Members column.

By "case insensitive," do you mean an MS Access front end won't break with
the back end tables on a Linux box, because they interface through SQL?

Thanks again!
 
Regardless of where the back-end file exists, Access is running on the
user's workstation, not the server.

To be honest, I don't know whether you can connect to a back-end hosted on a
Linux server, but if you can't, the issue definitely won't be because of
differences in Case.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)


donaldg said:
Thanks Douglas,

I've done a major purge of tables, forms and code; the only thing I can
think of is wherever the Object Browser gets its Members list from. If I
select the [author] Form in the Classes column, I see AuthorNotes in the
Members column.

By "case insensitive," do you mean an MS Access front end won't break with
the back end tables on a Linux box, because they interface through SQL?

Thanks again!

Douglas J Steele said:
You've probably got it as AuthorName somewhere still, and that's affecting
all of the references. However, VB code is case insensitive, so it really
shouldn't matter.
Click to expand...
Click to expand...
 
Douglas, you are the man--thanks.

Douglas J Steele said:
Regardless of where the back-end file exists, Access is running on the
user's workstation, not the server.

To be honest, I don't know whether you can connect to a back-end hosted on a
Linux server, but if you can't, the issue definitely won't be because of
differences in Case.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)


donaldg said:
Thanks Douglas,

I've done a major purge of tables, forms and code; the only thing I can
think of is wherever the Object Browser gets its Members list from. If I
select the [author] Form in the Classes column, I see AuthorNotes in the
Members column.

By "case insensitive," do you mean an MS Access front end won't break with
the back end tables on a Linux box, because they interface through SQL?

Thanks again!

Douglas J Steele said:
You've probably got it as AuthorName somewhere still, and that's affecting
all of the references. However, VB code is case insensitive, so it really
shouldn't matter.


--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)


I'm trying to correct a compatibility issue by changing the table and
field
names to all lowercase. In VB code, the control names automatically change
back to initial caps when I try to correct them.

For example, I enter:

Me!authornotes

As soon as I take the cursor off it, it reverts to:

Me!AuthorNotes

I've searched for hours trying to stop this--any assistance greatly
appreciated.
Click to expand...
Click to expand...
Click to expand...
 
Back
Top