Without YOUR code and YOUR data that sort of error really can't be addressed. The most common causes for the exception errors are usually pretty odd combinations of syntax and data.
And I asked about the spelling just in case. Nothing like providing data with the spelling of the variable one way and differently in another.
@Ms_Raza wrote:
@ballardw Thank a lot for replying and taking time to correct the syntax and for your suggestion!
Using date is definitely more useable than using weeks or year but unfortunately, I have need weekly averages for my exposure window. I have date in my original datafile. I agree with you on following proper practice to provide examples. Regarding the spelling of municipality. I don't why was it not obvious that it was a "typo".
When I ran your syntax on my data, using numerical date variable I got an error
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
The SAS task name is [SGPLOT]
ERROR: Read Access Violation SGPLOT
Exception occurred at (AA93560E)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
00007FFFAA93560E 00000074D0DF74C0 sasstgr:tkvercn1+0x845CE
00007FFFAA9554C7 00000074D0DF7500 sasstgr:tkvercn1+0xA4487
00007FFFAA93F737 00000074D0DF7570 sasstgr:tkvercn1+0x8E6F7
00007FFFAFEE4467 00000074D0DF7578 sasods:tkvercn1+0x273427
00007FFFAFCC5198 00000074D0DF7840 sasods:tkvercn1+0x54158
00007FFFAFCC0F6E 00000074D0DF79D0 sasods:tkvercn1+0x4FF2E
00007FFFAB0C1A97 00000074D0DF79D8 sassgplo:tkvercn1+0xC0A57
00007FFFAB03B092 00000074D0DFF4E0 sassgplo:tkvercn1+0x3A052
00007FFFDB4AF5A8 00000074D0DFF4E8 sashost:Main+0x15268
00007FFFDB4B59CC 00000074D0DFF810 sashost:Main+0x1B68C
00007FF8449C7034 00000074D0DFF818 KERNEL32:BaseThreadInitThunk+0x14
00007FF8458C26A1 00000074D0DFF848 ntdll:RtlUserThreadStart+0x21
Click image to register for webinar
