One to Many OLE Objects

G

Guest

OLE Object fields can't be made primary keys.

I have a table that houses many OLE Objects for one record and I want to
make sure that one record can NOT be related to any particular OLE Object
multiple times.

Typically, I use the multiple key "trick" to resolve this BUT since I can't
make the OLE Object field part of a multiple key configuration I'm at a loss.

Is there a way I can manage a one to many OLE Object relationship that will
assure no OLE Object will be related to one record more than once?

Thanks for any help you might have!!!
 
J

Jeff Boyce

John

OLEObjectTable
OLEObjectID (Autonumber)
OLEObject
...

"Main"Table
MainTableID (Autonumber)
OLEObjectID (foreign key, from OLEObjectTable)
...

Good luck!

Jeff Boyce
<Access MVP>
 
G

Guest

Thanks, Jeff!

Not sure if I'm following.

In the "Main Table" do I need to create a new MainTableID (Autonumber)? My
"Main Table" has a primary key already of txtProfileID which is a text field.
 
J

Jeff Boyce

I didn't know you already had a primary key. No need for another <g>.

Jeff Boyce
<Access MVP>
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top