@suztang wrote: Transitioning from SAS EG to SAS ViYa and Studio. In SAS EG, I could check a box during import to convert characters in a var name to make them SAS-compatible. The closest I can get to that in Studio is to use option validvarname=v7, except I don't want my variable names truncated. What's the code to replicate what SAS EG is doing with var names? Are you talking about about reading a TEXT file? Such as a CSV file?  Or do you have some other type of file, like an XLSX file?   What CODE are you using in EG?  Or did you use some GUI tool in EG?  Note that the GUI tool in EG for importing a TEXT file does analysis of the file on your PC and then uploads a (potentially) modified version of the file and the code to read it. What CODE are you using in SAS/Studio?  Or did you use some GUI tool to generate the code?   Can you run normal SAS code on your VIYA platform?  Perhaps you could use some other tool to GUESS how to convert the file in a dataset.  You could see if you can get this SAS macro to run on VIYA. https://github.com/sasutils/macros/blob/master/csv2ds.sas ... View more

@suztang wrote: The real common variable isn't actually a Char., it's a Date8., and it's Date8. in both tables. I am perplexed as this is not my first rodeo with merging and concatenating tables. Print some of the date values with a non-date format. If some of the values have decimal portion this is could happen and will not be visible when a date format like DOWNAME3 used. Date8. doesn't display anything resembling Sun, Date8 would display something like 16Mar12 and be right justified in 8 characters making it appear to have a leading space. So why did you show values like Sun????? if that is the format data example; x= 22222.01; y= 22222; put x= downame3. y= dowwname3. ; put x= date8. y= date8.; /* but obviously the values of x and y are different*/ run; And not telling sufficient detail about your data does not let us help you. I still say there is something different in the values. ... View more