Actuarial Outpost
 
Go Back   Actuarial Outpost > Actuarial Discussion Forum > Software & Technology
FlashChat Actuarial Discussion Preliminary Exams CAS/SOA Exams Cyberchat Around the World Suggestions

Search Actuarial Jobs by State @ DWSimpson.com:
AL AK AR AZ CA CO CT DE FL GA HI ID IL IN IA KS KY LA
ME MD MA MI MN MS MO MT NE NH NJ NM NY NV NC ND
OH OK OR PA RI SC SD TN TX UT VT VA WA WV WI WY

 
 
Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
  #23  
Old 03-18-2020, 12:22 PM
Maphisto's Sidekick's Avatar
Maphisto's Sidekick Maphisto's Sidekick is offline
Member
CAS
 
Join Date: Nov 2001
Location: South Park Genetics Lab
College: Ardnox
Favorite beer: The kind with alcohol
Posts: 3,509
Default

Quote:
Originally Posted by 1695814 View Post
I have query that joins two tables, ReservesCurr & ReservesPrev, by Policy.
In each table is a field called "Reserve".

In my output, it is (automatically) labeling those "Reserve" & "Reserve1".

I'd rather have it be something more descriptive. Even ReservesCurr.Reserve & ReservesPrev.Reserve would be useful.

I don't know how to do that.
In the query design screen, you can assign new field names to the output of the query

In the top row, one cell might read "ReservesCurr: [ReservesCurr].[Reserve]", while another cell might read "ReservesPrev: [ReservesPrev].[Reserve]".

By doing that, you assign field name "ReservesCurr" to the "Reserves" value coming from table ReservesCurr, and you assign field name "ReservesPrev" to the other one.

This tactic also comes in handy when doing aggregate queries, and you don't want automatic field names like "SumOfReserves".
Reply With Quote
 

Tags
access

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


All times are GMT -4. The time now is 08:57 AM.


Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
*PLEASE NOTE: Posts are not checked for accuracy, and do not
represent the views of the Actuarial Outpost or its sponsors.
Page generated in 0.81592 seconds with 11 queries