Re: Access and 'Many to One Relationships'

TobyR — Sun, 14 Mar 2010 16:28:55 GMT

So, I've found out that the primary table needs to be the 'one' part of the 'one/many' relationship. At first glance that seems to destroy my planned design but most probably it just means I have to research more to find out how to achieve what I want to do.

Access and 'Many to One Relationships'

TobyR — Sun, 14 Mar 2010 13:43:18 GMT

I've just started trying to use Infopath with Access (knowing a bit about Access, and only a very little about Infopath, though to be fair it seems quite intuitive). To get a feel for it I created a very simple database and then followed the Inforpath in-bulit help to create a form. All seemed OK except when I completed the connection there was a statement on the confirmatory pop-up saying to the effect 'Submitting: disabled- there might be a many to one relationship'. I checked this forum and found advice that this message could appear if there was not at least one record in each Access table. So I added a dummy record to each table and tried again. Same message. I tried again, with just one (primary) table, and as you would expect it worked OK (there being no realtionships!). But by adding just one more table, with a realtionship, and I get the same message again. The linking field in the secondary table is a primary key (autonumber, no duplicates), and the related field in the 'primary' table is a foreign key field (type number, duplicates OK). All advice and help appreciated!

Microsoft Access

Re: Access and 'Many to One Relationships'

Access and 'Many to One Relationships'