>>I still type the periods around .AND. & .OR. use -> to separate tables and fields.
>
>I am oldfashioned... but there are limits. I did keep .and. and .or. and I think even .not. for a year or two after they became optional, but even then I always surrounded them with syntactically unnecessary spaces. Then, well, if spaces are delimiters, what are the dots for? Also, using those dots without spaces can be mistaken by the compiler if there's an alias, field, object reference or a PEM on the other side of the dot, which makes that space less optional. So I forgot the .and. and went for and, eventually.
>
>-> is a different story. I poured myself a drink when I was able to replace it with a dot, and never looked back. It was just very clumsy syntax for something you have to type so of

I'm slowly going away from it because SQL Server doesn't like a query passed up to it with .NOT., .AND., .OR. and -> for separators.