MS ACCESS 2000 and long names on querys/tables?

[stigejg]

Hello out there,

Anyone who can give me a litle hint about this?

I am working with my Access 97, making databases and querys and having long and describing names on my querys (wery understanable for me and other with the same database).

But now have some of my colleagues started to purchase Access 2000 (good for them, bad for me because I have no experience with Access 2000).

It seem that Access 2000 dont like my nice and long querynames.

So my big question are: Is there a way round this problem (it semms that Access 2000 just alow 20 characters names). Is it posible for me to increace the alowed number of characters or must I rename all my querys?

Best regard

Stig

 

[930driver]

The following is from Access 2000 Help:

Guidelines for naming fields, controls, and objects
Names of fields, controls, and objects in Microsoft Access:

Can be up to 64 characters long.


Can include any combination of letters, numbers, spaces, and special characters except a period (.), an exclamation point (!), an accent grave (`), and brackets ([ ]).


Can't begin with leading spaces.


Can't include control characters (ASCII values 0 through 31).


Can't include a double quotation mark (&quot in table, view, or stored procedure names in a Microsoft Access project.
Although you can include spaces in field, control, and object names, most examples in the Microsoft Access documentation show field and control names without spaces because spaces in names can produce naming conflicts in Visual Basic for Applications in some circumstances.

When you name a field, control, or object, it's a good idea to make sure the name doesn't duplicate the name of a property or other element used by Microsoft Access; otherwise, your database can produce unexpected behavior in some circumstances. For example, if you refer to the value of a field called Name in a table NameInfo using the syntax NameInfo.Name, Microsoft Access displays the value of the table's Name property rather than the value of the Name field.

Another way to avoid unexpected results is to always use the ! operator instead of the . (dot) operator to refer to the value of a field, control, or object. For example, the following identifier explicitly refers to the value of the Name field rather than the Name property:

[NameInfo]![Name]

"The Key, The Whole Key, and Nothing But The Key, So Help Me Codd!"