>We just ran into an interesting call from a customer that may be of some help of you in the future (actually it's a problem from the past). The call went something like this. All my reports run fine until today when I added a new user to the system and logged on as that user. Then I get an XBase Error when I click print.
>
>Next question. What user did you add? The reply, "User name is J and login name is J. No password".
>
>A little about our system. we use the standard MM framework stuff for users and groups. first reaction, must be Kevins fault! :)
>
>Next step, recreate the error. We use a test account on our development boxes with a login of L. So that should be a good test. We login as L, everything works fine. I would have bet the farm that it was that 1 character login causing the problem.
>
>Next step, create user J. We login as J, BOOM! Index tag not found when we run the report.
>
>Now for some more on what we are doing. We have a reportobj that has a method on it called BuildData(). This method creates a free table and gathers all the info from other tables and fills the free table. So what would you name that free table? We chose to go with the user login name. Seeing a problem yet?
>
>Why would a free table name of L work and a free table name of J blow up? You old guys are already smiling. In the BuildData method we created the Table named J, then Selected a different work area and did some stuff. then when we ready to run the report, we had Select(cTableName), where cTablename was J. What happens when you select L? What happens when you select J?
>
>I'll leave it there and see if you new guys get it. :) One more hint. A login of B blows up also.

I don't use MM framework, but I believe that has something to do with the fact stated in Help for SELECT command:

"You can also include a letter from A through J for cTableAlias to activate one of the first ten work areas."