SOLVED

Table Alias in Access 2019

%3CLINGO-SUB%20id%3D%22lingo-sub-1365543%22%20slang%3D%22en-US%22%3ETable%20Alias%20in%20Access%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1365543%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20Access%202016%20and%20earlier%2C%20in%20a%20query%2C%20you%20can%20set%20an%20alias%20for%20a%20table%20by%20clicking%20on%20the%20table%20and%20showing%20the%20Property%20Sheet.%26nbsp%3B%20This%20opened%20what%20used%20to%20be%20the%20%22Field%20List%20Properties%22%20with%20a%20%22General%22%20tab%20with%20two%20properties%3A%26nbsp%3B%20Alias%20and%20Source.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20my%20new%20Access%202019%2C%20I%20cannot%20bring%20up%20this%20%22table%22%20Property%20Sheet!%26nbsp%3B%20When%20I%20click%20on%20the%20table%20and%20bring%20up%20the%20properties%2C%20I%20am%20seeing%20the%20properties%20of%20the%20last%20selected%20query%20object.%26nbsp%3B%20Clicking%20on%20the%20table%20does%20not%20change%20the%20property%20window.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20setting%20I%20have%20wrong%20in%20my%20new%20Access%202019%3F%26nbsp%3B%20Did%20MS%20do%20away%20with%20the%20Field%20List%20Properties%20for%20tables%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20apparently%20can%20go%20into%20SQL%20and%20create%20an%20alias%20there%20that%20will%20be%20reflected%20in%20the%20QBE%20grid%2C%20but%20I%20have%20no%20idea%20how%20to%20change%20it%20in%20the%20QBE%20interface!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1365543%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAccess%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1365695%22%20slang%3D%22en-US%22%3ERe%3A%20Table%20Alias%20in%20Access%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1365695%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F658588%22%20target%3D%22_blank%22%3E%40MarySmith2020%3C%2FA%3E%26nbsp%3BThis%20is%20a%20known%20bug%20introduced%20in%20a%20recent%20update.%20I'll%20verify%20if%20there's%20a%20fix%20and%20post%20back%20what%20I%20find.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1365707%22%20slang%3D%22en-US%22%3ERe%3A%20Table%20Alias%20in%20Access%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1365707%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F46682%22%20target%3D%22_blank%22%3E%40George%20Hepworth%3C%2FA%3E%26nbsp%3B%20That%20would%20be%20awesome!%26nbsp%3B%20Well%2C%20you%20testing%20it...%20not%20that%20it%20is%20possibly%20a%20bug.%26nbsp%3B%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1365729%22%20slang%3D%22en-US%22%3ERe%3A%20Table%20Alias%20in%20Access%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1365729%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F658588%22%20target%3D%22_blank%22%3E%40MarySmith2020%3C%2FA%3E%26nbsp%3BI%20found%20where%20it%20has%20been%20reported%20to%20the%20MS%20Access%20team%20at%20Microsoft%20and%20they%20are%20investigating%20it.%20I%20don't%20know%20when%20a%20fix%20will%20be%20available.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1365744%22%20slang%3D%22en-US%22%3ERe%3A%20Table%20Alias%20in%20Access%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1365744%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F46682%22%20target%3D%22_blank%22%3E%40George%20Hepworth%3C%2FA%3E%26nbsp%3BThank%20you.%26nbsp%3B%20At%20least%20you%20can%20get%20the%20query%20design%20window%20to%20take%20a%20brute-forced%20SQL%20alias%20and%20show%20it%20and%20use%20it%20in%20the%20QBE%20field%20list.%26nbsp%3B%20How%20can%20something%20like%20this%20happen%3F%26nbsp%3B%20I'm%20really%20surprised%20that%20I%20could%20not%20find%20mention%20of%20it%20in%20my%20google%20searches.%26nbsp%3B%20Thanks%20again.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

In Access 2016 and earlier, in a query, you can set an alias for a table by clicking on the table and showing the Property Sheet.  This opened what used to be the "Field List Properties" with a "General" tab with two properties:  Alias and Source.

 

In my new Access 2019, I cannot bring up this "table" Property Sheet!  When I click on the table and bring up the properties, I am seeing the properties of the last selected query object.  Clicking on the table does not change the property window.

 

Is there a setting I have wrong in my new Access 2019?  Did MS do away with the Field List Properties for tables??

 

I apparently can go into SQL and create an alias there that will be reflected in the QBE grid, but I have no idea how to change it in the QBE interface!

4 Replies
Highlighted

@MarySmith2020 This is a known bug introduced in a recent update. I'll verify if there's a fix and post back what I find.

Highlighted

@George Hepworth  That would be awesome!  Well, you testing it... not that it is possibly a bug.  :)

Highlighted
Best Response confirmed by MarySmith2020 (New Contributor)
Solution

@MarySmith2020 I found where it has been reported to the MS Access team at Microsoft and they are investigating it. I don't know when a fix will be available. 

Highlighted

@George Hepworth Thank you.  At least you can get the query design window to take a brute-forced SQL alias and show it and use it in the QBE field list.  How can something like this happen?  I'm really surprised that I could not find mention of it in my google searches.  Thanks again.