Correct. Tables and queries share the same namespace.

Post #152,620 by rickw 4/26/04 12:07:28 PM Reply	Correct. Tables and queries share the same namespace. It's always been that way. Hungarian notation is a bit helpful here. I guess qualifying an object name was considered to be more trouble than having a shared namespace. FAQ! We're scrod!
Post #152,634 by acagle 4/26/04 1:07:56 PM Reply	Re: Correct. Tables and queries share the same namespace. Ya, I finally figured that out. Sorry, went ballistic on that one. The combination of XP and Orifice 2003 has just caused my whole system to go to hell recently. I'm about to reboot for the umpteenth time in the last couple of weeks because XP tells me via error message that it can't find an MDB file which is clearly there and which it subsequently opens with no problem. Monday I was happily making changes to a database and copying the files to the users' Win98 local drives, and Tuesday after doing the same, it just plain stopped working and completely bombed out of their Access versions. Then certain of MY MDBs refused to display the code in the code window and blanked out the option to show the code. I'd go into the excitement of attempting to de-install everything related to Orifice, but that would require several pages, 2-part harmonies, and a Greek chorus lamenting the human condition. Back I go to my Sysiphean task of trying to make XP/Orifice do something useful. . . .
Post #153,862 by rickw 5/5/04 1:55:48 PM Reply	Yeah...me too... I have a contractlet right now where somebody (AGAIN) is paying me because they found out that Excel isn't a DBMS. So, they want Access. Since I'm getting back into the market after about 2 years out, this is actually a decent scope for me right now. Access has been using about 80 percent of my CPU time for the last 20 minutes. My crime? Query\|New. I have no idea what the fuck it's doing. This database is fairly big for Access (~900MB), I wish I could use something better but it won't happen. So maybe it arbitrarily decided that now was the time to optimize something. Maybe it's in a loop. Maybe it's background processing SETI data. Maybe it's downloading database porn and gratifying itself. No way of knowing of course, no monitoring, no logs, no current activity to look at, jack shit. Killing the process would solve the problem if it's just abcess looping or playing with itself or whatever but then I'd have to wait for it to repair the database, which is a lot to ask with a database of this size and a manager of this quality. Fuck. FAQ! We're scrod!
Post #153,864 by Another Scott 5/5/04 1:59:55 PM Reply	ICLRPD (new thread) Created as new thread #153863 titled [link\|/forums/render/content/show?contentid=153863\|ICLRPD]

Welcome to IWETHEY!