Post #152,371
4/23/04 1:34:08 PM
4/23/04 1:48:19 PM
|
Beware Access 2003.
I believe it is fundamentally f*cked. I just ran a Make Table query, and it deleted the underlying query it was based on. Among other screwy problems.
I woulda thought this version was okay, since they usually have a crappy version (Access 95, 2000) alternating with okay ones (2.0, 97).
Not impressed so far.
And the whole look-and-feel of Orifice 2003 just plain looks cartoonish to me. If they're going to steal from the Mac, at least be somewhat tasteful in doing so.
Update: Apparently, one cannot give a query and a table the same name.
Edited by acagle
April 23, 2004, 01:48:19 PM EDT
|
Post #152,386
4/23/04 3:10:55 PM
|
Access 2002 does that too.
Running a Make Table query that makes a table with the same name as the query will delete the query out from under itself. It does ask you if you want to do it (Yes/No), but I can't imagine why one would want to.
I agree on the look, though it looks alot better IMHO with the Silver theme.
--
Chris Altmann
|
Post #152,424
4/23/04 9:51:43 PM
|
Unique constraint is to blame.
At least in Access 2000 and before. Show hidden objects off the tool menu. Look at the MSysObjects table. There's a unique constraint on the Name + ParentId. All the foo in the .mdb has the same parentid, so if you name a query and a table the same thing - well, last one in wins.
bcnu,
Mikem
|
Post #152,620
4/26/04 12:07:28 PM
|
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
4/26/04 1:07:56 PM
|
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
5/5/04 1:55:48 PM
|
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
5/5/04 1:59:55 PM
|
ICLRPD (new thread)
Created as new thread #153863 titled [link|/forums/render/content/show?contentid=153863|ICLRPD]
|
Post #152,893
4/28/04 12:29:59 PM
|
Access Weird Behavior #233.
The "Linked Table Manager" is not showing any of my linked tables. Any linked tables.
I tried converting both MDBs to 2002-2003 format, still no linked tables.
I tried creating a new linked table, still no linked tables. In fact, no MDB I've looked at will show any linked tables in the "Linked Table Manager" at all.
|
Post #152,896
4/28/04 12:42:11 PM
|
Note: It's a bug.
Fancy that. 9 years and we're still in dll hell.
[link|http://support.microsoft.com/default.aspx?scid=kb;en-us;835519|http://support.micro...d=kb;en-us;835519]
|
