Expr1: [FieldName] Problems

[dsfcom]

I am having some trouble with importation of queries which exhibits seemingly random occurences of query fields being renamed to "Expr1: [FieldName]" after import.

[FieldName] references the original field name

Does this occur because of the import process? There were no users connected during import and I have read a few posts concerning problems with logged on users during import but this was not happenning in my case.

Any other ways to avoid this situation?

Thanks!

 

[vbaInet]

Are you importing the queries from one Access db to another? What versions of Access are these dbs?

 

[dsfcom]

Yes...one db to another via Access2007 with Access2003 dbs (*.mdb). While fixing the fields I believe I may have found the problem. Some of my queries are based on tables that do not always exist and from reading related posts it seems this may be causing my issue. Does this seem likely?

 

[MSAccessRookie]

I am having some trouble with importation of queries which exhibits seemingly random occurences of query fields being renamed to "Expr1: [FieldName]" after import.

[FieldName] references the original field name

Does this occur because of the import process? There were no users connected during import and I have read a few posts concerning problems with logged on users during import but this was not happenning in my case.

Any other ways to avoid this situation?

Thanks!

Most of the time, this condition represents one of three situations.

1. The Imported Field has a Special Character in its Name
2. The imported Field has a Reserved Word in its Name
3. The imported Field is the result of a calculation of two or more other Fields, and has not been provided an Alias.

I placed them in the order that I have encountered them the most frequently. Although I am sure there are other possible reasons, eliminating these three might be a good place to start.

-- Rookie

 

[MSAccessRookie]

Yes...one db to another via Access2007 with Access2003 dbs (*.mdb). While fixing the fields I believe I may have found the problem. Some of my queries are based on tables that do not always exist and from reading related posts it seems this may be causing my issue. Does this seem likely?

This would probably create the problem if it were the condition.

 

[dsfcom]

Thanks Rookie. I will keep this in mind in future development. Good to know!

 

[JayLobos]

We have the same issue, but with a little variance...

We have temporary tables that are build on the fly, but some of these temporary tables have queries using them. Because these tables do not exist until right before the query is run or opened and are cleaned up after the process completes, they never exist for any extended period of time. Anyone have any idea how to stop Access 2010 from trying to autocorrect/alias these fieldnames to Expr1, Expr2, Expr3, etc...

We are praying for a setting that we can tweak, but I have found nothing yet.

Thanks for the help,

Jason

 

[boblarson]

Try not to post the same question more than once Jason. And, it is best to post your own question instead of adding to the existing thread, if the existing thread has not helped.