Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

Enforce referential integrity

Discussion in 'Information Technology' started by Blinda, Jul 28, 2006.

  1. Blinda

    Blinda
    Expand Collapse
    Guest

    Hi all,

    When I creat a relationship between a primary parent table to a child table,
    I have the following information:

    The operation failed. There are too many indexes on "parent table", delete
    some of the indexes on the "parent" table and try the operation again.

    What is the probelm? I have no problem at all for all the other child tables.

    Please help, thanks,

    Blinda
     
  2. Loading...


  3. John Vinson

    John Vinson
    Expand Collapse
    Guest

    On Tue, 6 Jun 2006 16:50:02 -0700, Blinda
    <Blinda@discussions.microsoft.com> wrote:

    >Hi all,
    >
    >When I creat a relationship between a primary parent table to a child table,
    >I have the following information:
    >
    >The operation failed. There are too many indexes on "parent table", delete
    >some of the indexes on the "parent" table and try the operation again.
    >
    >What is the probelm? I have no problem at all for all the other child tables.


    It's an Access limitation, a very annoying one for some complex
    database designs: a Table can have no more than 32 indexes. Check this
    table's Indexes - are there any redundant ones? In particular, some
    versions of Access automatically index some fields based on the
    fieldname; Lookup Fields create a redundant extra index; you may be
    able to use a compound index on two or three fields (e.g. LastName,
    FirstName, MiddleName) rather than three separate indexes.

    John W. Vinson[MVP]
     
  4. Blinda

    Blinda
    Expand Collapse
    Guest

    Thank you. I will try this.

    "John Vinson" wrote:

    > On Tue, 6 Jun 2006 16:50:02 -0700, Blinda
    > <Blinda@discussions.microsoft.com> wrote:
    >
    > >Hi all,
    > >
    > >When I creat a relationship between a primary parent table to a child table,
    > >I have the following information:
    > >
    > >The operation failed. There are too many indexes on "parent table", delete
    > >some of the indexes on the "parent" table and try the operation again.
    > >
    > >What is the probelm? I have no problem at all for all the other child tables.

    >
    > It's an Access limitation, a very annoying one for some complex
    > database designs: a Table can have no more than 32 indexes. Check this
    > table's Indexes - are there any redundant ones? In particular, some
    > versions of Access automatically index some fields based on the
    > fieldname; Lookup Fields create a redundant extra index; you may be
    > able to use a compound index on two or three fields (e.g. LastName,
    > FirstName, MiddleName) rather than three separate indexes.
    >
    > John W. Vinson[MVP]
    >
     
  5. aaron.kempf@gmail.com

    aaron.kempf@gmail.com
    Expand Collapse
    Guest

    32 indexes?

    bunch of friggin idiots

    throw away MDB and use Access Data Projects; the index tuning wizard
    and database tuning advisor do a much much better job than is possibly
    by hand.

    -Aaron



    Blinda wrote:
    > Thank you. I will try this.
    >
    > "John Vinson" wrote:
    >
    > > On Tue, 6 Jun 2006 16:50:02 -0700, Blinda
    > > <Blinda@discussions.microsoft.com> wrote:
    > >
    > > >Hi all,
    > > >
    > > >When I creat a relationship between a primary parent table to a child table,
    > > >I have the following information:
    > > >
    > > >The operation failed. There are too many indexes on "parent table", delete
    > > >some of the indexes on the "parent" table and try the operation again.
    > > >
    > > >What is the probelm? I have no problem at all for all the other child tables.

    > >
    > > It's an Access limitation, a very annoying one for some complex
    > > database designs: a Table can have no more than 32 indexes. Check this
    > > table's Indexes - are there any redundant ones? In particular, some
    > > versions of Access automatically index some fields based on the
    > > fieldname; Lookup Fields create a redundant extra index; you may be
    > > able to use a compound index on two or three fields (e.g. LastName,
    > > FirstName, MiddleName) rather than three separate indexes.
    > >
    > > John W. Vinson[MVP]
    > >
     
  6. Blinda

    Blinda
    Expand Collapse
    Guest

    Thank you. Could you please let me know how to use Access Data Projects? What
    will be the server name for my owner computer? How can I tell if I have MSDE
    or not for the "Data Link Properties" dialogue set up?

    Thanks,

    Blinda

    "aaron.kempf@gmail.com" wrote:

    >
    > 32 indexes?
    >
    > bunch of friggin idiots
    >
    > throw away MDB and use Access Data Projects; the index tuning wizard
    > and database tuning advisor do a much much better job than is possibly
    > by hand.
    >
    > -Aaron
    >
    >
    >
    > Blinda wrote:
    > > Thank you. I will try this.
    > >
    > > "John Vinson" wrote:
    > >
    > > > On Tue, 6 Jun 2006 16:50:02 -0700, Blinda
    > > > <Blinda@discussions.microsoft.com> wrote:
    > > >
    > > > >Hi all,
    > > > >
    > > > >When I creat a relationship between a primary parent table to a child table,
    > > > >I have the following information:
    > > > >
    > > > >The operation failed. There are too many indexes on "parent table", delete
    > > > >some of the indexes on the "parent" table and try the operation again.
    > > > >
    > > > >What is the probelm? I have no problem at all for all the other child tables.
    > > >
    > > > It's an Access limitation, a very annoying one for some complex
    > > > database designs: a Table can have no more than 32 indexes. Check this
    > > > table's Indexes - are there any redundant ones? In particular, some
    > > > versions of Access automatically index some fields based on the
    > > > fieldname; Lookup Fields create a redundant extra index; you may be
    > > > able to use a compound index on two or three fields (e.g. LastName,
    > > > FirstName, MiddleName) rather than three separate indexes.
    > > >
    > > > John W. Vinson[MVP]
    > > >

    >
    >
     
  7. John Vinson

    John Vinson
    Expand Collapse
    Guest

    On Wed, 7 Jun 2006 11:39:03 -0700, Blinda
    <Blinda@discussions.microsoft.com> wrote:

    >Thank you. Could you please let me know how to use Access Data Projects? What
    >will be the server name for my owner computer? How can I tell if I have MSDE
    >or not for the "Data Link Properties" dialogue set up?


    Blinda, you should be aware that Aaron is a notorious troll in these
    newsgroups. He despises Access and the JET database engine, and
    apparently posts primarily to denigrate them and recommend SQL/Server
    in its various guises.

    You can certainly develop using MSDE, and it may even help with this
    particular issue - but it's not a cure-all and can be more complex to
    use.

    John W. Vinson[MVP]
     
  8. Blinda

    Blinda
    Expand Collapse
    Guest

    Thank you. I tried your way, it really workd. Thanks.

    "John Vinson" wrote:

    > On Wed, 7 Jun 2006 11:39:03 -0700, Blinda
    > <Blinda@discussions.microsoft.com> wrote:
    >
    > >Thank you. Could you please let me know how to use Access Data Projects? What
    > >will be the server name for my owner computer? How can I tell if I have MSDE
    > >or not for the "Data Link Properties" dialogue set up?

    >
    > Blinda, you should be aware that Aaron is a notorious troll in these
    > newsgroups. He despises Access and the JET database engine, and
    > apparently posts primarily to denigrate them and recommend SQL/Server
    > in its various guises.
    >
    > You can certainly develop using MSDE, and it may even help with this
    > particular issue - but it's not a cure-all and can be more complex to
    > use.
    >
    > John W. Vinson[MVP]
    >
     
  9. aaron.kempf@gmail.com

    aaron.kempf@gmail.com
    Expand Collapse
    Guest

    it's not more complex; it WORKS without fail.
    MDB half works; half the time.

    how many times have you stacked a query on top of a query and had it
    'just crap out' in mdb?

    how long does it take to append 5,000 records into Sharepoint via MDB?

    there are better things to do with your efforts than sittting around
    and learning obsolete database formats.

    Access doesn't use memory effectively.

    A gigabyte of memory costs what, $60?
    Access can't use the most important component in your PC.

    SQL Server uses it quite well.

    ADP is a cure all
    MDB is a piece of shit database for piece of shit obsolete gray haired
    assholes in wheelchairs.

    oh sonny.. help me with this relationships window; will you??

    GAG

    grow the {censored word, do not repeat.} up kids and start pushign a real database.
    MDB is whack.

    instead of spending all your time compacting and repairing..

    {censored word, do not repeat.} you john

    {censored word, do not repeat.} you and {censored word, do not repeat.} your hairy fat mother

    in order to determine if you have msde:

    a) start, run, services.msc
    b) look for something called 'microsoft sql server (mssqlserver$msde)
    or something along those lines
    c) if it is there; but not started; then right-click to start the
    service
    d) if it isn't there then download 'SQL Server Desktop Engine' from
    www.microsoft.com/sql
    e) i would reccomend using ADP for a while and then growing up into Sql
    Server Management Studio. SSMS is a great tool-- but the access 'query
    by design' window is a tremendous help to newbies

    I just think that you can choose the easy road or you can choose the
    right road.

    MDB engine is not appropriate; it is not scalable enough-- for a single
    record and a single user.

    I'm sorry that this JOHN VINSON jerk thinks that it is appropriate to
    badmouth SOMEONE WHO IS RIGHT.

    Maybe if the world wasn't filled with pussies like john vinson; then
    maybe corporate america could find the resources they need. As it is;
    America needs about a million more database engineers.

    And jerking off and playing with MDB files; that isn't the right way to
    'get a real job'

    grow up John and stop playing with obsolete MDB files.

    it makes me sick that you stupid old {censored word, do not repeat.} can't bother to learn a real
    database like MSDE, SQL Server; etc.

    Even mySql for all I care.

    -Aaron



    John Vinson wrote:
    > On Wed, 7 Jun 2006 11:39:03 -0700, Blinda
    > <Blinda@discussions.microsoft.com> wrote:
    >
    > >Thank you. Could you please let me know how to use Access Data Projects? What
    > >will be the server name for my owner computer? How can I tell if I have MSDE
    > >or not for the "Data Link Properties" dialogue set up?

    >
    > Blinda, you should be aware that Aaron is a notorious troll in these
    > newsgroups. He despises Access and the JET database engine, and
    > apparently posts primarily to denigrate them and recommend SQL/Server
    > in its various guises.
    >
    > You can certainly develop using MSDE, and it may even help with this
    > particular issue - but it's not a cure-all and can be more complex to
    > use.
    >
    > John W. Vinson[MVP]
     

Share This Page