invisible appearing point

[dr_Logos]

1 ;*';*";*/;quit;run;
2 OPTIONS PAGENO=MIN;
3 PROC SQL NOEXEC;
4 SELECT t1.'QW'n,
5 t1.'QW'n,
6 t1.'QE'n
7 FROM
7 ! WORK.'.'B2'
_
49
___
22
___
76
7 ! n t2
8 RIGHT JOIN WORK.'11'n t1 ON (t2.'FC'n = t1.'FLа'n);
______________ _________
49 49
NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release. Inserting white space
between a quoted string and the succeeding identifier is recommended.

ERROR 22-322: Expecting a name.

ERROR 76-322: Syntax error, statement will be ignored.

9 QUIT;
10 QUIT; RUN;
11

7 ! WORK.'.'B2' in original name have not dot: "WORK.B2"

WTF?

invisible appearing point at the same time, for some reason, in the project now, when joining any tables, this error occurs (showing at the same time an extra point, which does not physically exist)

Please help please understand and remove the formation of these points, which do not. 

[Kurt_Bremser]

Since your names are all valid for SAS V7, you don't need the name literals. Remove them all, and look at the coloring of the Enhanced Editor to find any remaining unbalanced quotes.

[VDD]

maybe this line is missing the quote

7 ! WORK.'.'B2'

[Tom]

Retype the line and see if that fixes the issue.

FROM WORK.B2 t2

Note no need use a name literal for B2.  But if you do have strangely named tables then make sure that the VALIDMEMNAME option is set to EXTEND.

[Tom]

 in the project now, when joining any tables, this error occurs (showing at the same time an extra point, which does not physically exist)

What does that mean? Are you using Enterprise Guide or some other tool to generate code for you?

Or are you typing the code into an editor?  Like the SAS editor in Display Manager (or the Enhanced Editor in Display Manager in PC SAS)?  Or edit pane in SAS/Studio?

Have you somehow turned on VALIDMEMNAME=EXTAND and managed to create a dataset whose member name is literally

.'B2

and are then using some type of point and click tool to generate SQL code that is converting is trying to convert that into an name literals and instead making this gibberish

'.'B2'n

[dr_Logos]

Yes. i  am use SAS EG. 

Origanl name table only " WORK.B2" but code in reading SAS EG see this for " WORK..B2" wtf?

[VDD]

your problem is that you have quotes and double quotes that are unbalanced.  line 1 and line 7.  WTF statements are un-expectable.  You should review your work, make sure that you are seeing what is really there.  enlarge you view so that you can see what you may need a magnifying glass to see with the small print.

[Tom]

Did you try resetting your SAS session?  One problem with tools like EG that connect to a SAS session is that you only see pieces of the full SAS log and so previous errors that might have left SAS in an unexpected state can cause valid code to appear invalid because of the state SAS was already in when it tried to interpret the new code.

Next: If you are submitting code (either written by you or someone else) then review the code you are submitting carefully.  As I said re-type the code to make sure there are not hidden characters that the editor is not showing you.

If instead the code is being generated by EG in response to you clicking on buttons then you need to show exactly what steps you used to get that code submitted.