A Windows Vista forum. Vista Banter

Welcome to Vista Banter.

You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!

If you have any problems with the registration process or your account login, please contact contact support.

Go Back   Home » Vista Banter forum » Microsoft Windows Vista » Hardware and Windows Vista
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Hardware and Windows Vista Hardware issues in relation to Windows Vista. (microsoft.public.windows.vista.hardware_devices)

ACCESS 2003 Linking Tables Roadblock- PLEASE HELP!!!!!!!



 
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old June 19th 08, 06:00 PM posted to microsoft.public.windows.vista.hardware_devices
Jana
external usenet poster
 
Posts: 14
Default ACCESS 2003 Linking Tables Roadblock- PLEASE HELP!!!!!!!

have a major problem. I am developing a database for a client that contains
over 302 tables, all of which have thousands of rows. 301 of these tables
need to be linked to the parent table, and all have the same primary key.
However, I have recieved that evil error message that only 32 tables can be
indexed. I have searched and searched, but cannot find a solution to this.
I am desperate for any suggestions, even if it means taking avenues other
than ACCESS 2003. The only requirements are that the database has the
ability to be online, collecting data from other parties via some sort of
form. Also, these tables must have full capabilities to be edited and
controlled, not read-only. CAN ANYONE HELP ME??? There is a huge deadline
coming in hours. Thanks!
  #2 (permalink)  
Old June 19th 08, 06:21 PM posted to microsoft.public.windows.vista.hardware_devices
Curious
external usenet poster
 
Posts: 375
Default ACCESS 2003 Linking Tables Roadblock- PLEASE HELP!!!!!!!

Sounds like you need a major design change is required.
How about creating less tables that have to be linked and then have the
different Access forms you develop for some of the tables prefill in the
fields that contain the IDs and other information unique to the party that
is using the form.
"Jana" wrote in message
...
have a major problem. I am developing a database for a client that
contains
over 302 tables, all of which have thousands of rows. 301 of these tables
need to be linked to the parent table, and all have the same primary key.
However, I have recieved that evil error message that only 32 tables can
be
indexed. I have searched and searched, but cannot find a solution to
this.
I am desperate for any suggestions, even if it means taking avenues other
than ACCESS 2003. The only requirements are that the database has the
ability to be online, collecting data from other parties via some sort of
form. Also, these tables must have full capabilities to be edited and
controlled, not read-only. CAN ANYONE HELP ME??? There is a huge
deadline
coming in hours. Thanks!


  #3 (permalink)  
Old June 19th 08, 07:37 PM posted to microsoft.public.windows.vista.hardware_devices
David B.[_3_]
external usenet poster
 
Posts: 649
Default ACCESS 2003 Linking Tables Roadblock- PLEASE HELP!!!!!!!

I would suggest repost in an Access group as this has nothing to do with
Vista hardware.

--

----
Crosspost, do not multipost http://www.blakjak.demon.co.uk/mul_crss.htm
How to ask a question http://support.microsoft.com/kb/555375



"Jana" wrote in message
...
have a major problem. I am developing a database for a client that
contains
over 302 tables, all of which have thousands of rows. 301 of these tables
need to be linked to the parent table, and all have the same primary key.
However, I have recieved that evil error message that only 32 tables can
be
indexed. I have searched and searched, but cannot find a solution to
this.
I am desperate for any suggestions, even if it means taking avenues other
than ACCESS 2003. The only requirements are that the database has the
ability to be online, collecting data from other parties via some sort of
form. Also, these tables must have full capabilities to be edited and
controlled, not read-only. CAN ANYONE HELP ME??? There is a huge
deadline
coming in hours. Thanks!


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 08:58 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.Search Engine Optimization by vBSEO 3.0.0 RC6
Copyright ©2004-2024 Vista Banter.
The comments are property of their posters.