C
Crockett
I have a user (developer), Windows 2000 with Office XP, that does most of his
work in Access. When he tries to create a new query in an existing database
using the design view and if the number of existing tables, or queries, or
those listed under both exceed the amount that will fit in the window before
the scroll bar appears, the window displays either a couple of the existing
entries or is blank. We have played with this to the point that if 13
entries are listed under the tables tab, query tab, or both tab, everything
is fine. But if we create say a 14th table and then try to do a new query in
the design view, the tables tab is all screwed up but the query tab and both
tab are fine. Likewise, if we have 14 queries to display or the number of
items under the both tab is more than 13, they will be screwed up. My
apologies if I am not being clear but it is hard to explain. We have tried
this with several different databases and it is consistent. I have tried
doing a Detect and Repair as well as uninstalling and reinstalling the entire
Office XP suite but neither of those helped. I think that this may be a
problem with Windows 2000. Any help or suggestions would be greatly
appreciated.
work in Access. When he tries to create a new query in an existing database
using the design view and if the number of existing tables, or queries, or
those listed under both exceed the amount that will fit in the window before
the scroll bar appears, the window displays either a couple of the existing
entries or is blank. We have played with this to the point that if 13
entries are listed under the tables tab, query tab, or both tab, everything
is fine. But if we create say a 14th table and then try to do a new query in
the design view, the tables tab is all screwed up but the query tab and both
tab are fine. Likewise, if we have 14 queries to display or the number of
items under the both tab is more than 13, they will be screwed up. My
apologies if I am not being clear but it is hard to explain. We have tried
this with several different databases and it is consistent. I have tried
doing a Detect and Repair as well as uninstalling and reinstalling the entire
Office XP suite but neither of those helped. I think that this may be a
problem with Windows 2000. Any help or suggestions would be greatly
appreciated.