Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Date fields in a Composite Key

Hi all,

I have created a composite key which includes the date field ,interval and calltypekey however the dates are not appearing the same in both tables resulting in my data from the two tables not associating correctly. I believe this is a Date formatting issue but both date fields are 'Date' in the SQL Server.

I have tried date() and Date#() but neither have worked.

I need the comp key and date to match what is in  'AggData'

AggData

Date Problem.PNG

OrgData

Date Problem 2.PNG

Any help would be greatly appreciated.

Thanks,

Donna

1 Solution

Accepted Solutions
Gysbert_Wassenaar

Try using the num function to turn the date strings of the AggData table into numeric values like in the OrgData table. If that doesn't work then they're not dates but strings. In that case use num(date#( Date2, 'DD/MM/YYYY'))


talk is cheap, supply exceeds demand

View solution in original post

2 Replies
Gysbert_Wassenaar

Try using the num function to turn the date strings of the AggData table into numeric values like in the OrgData table. If that doesn't work then they're not dates but strings. In that case use num(date#( Date2, 'DD/MM/YYYY'))


talk is cheap, supply exceeds demand
Not applicable
Author

This works Thank you !

I was able to change it within the composite key.

Thanks for the help