Without knowing the details of the application, I can't be more definite
than: if each response is creating a new record (as seems likely) then you
should not have record conflicts. 42 users is not too many for a
well-designed, well-implemented multiuser application; in fact, it seems
likely that you may have very few users logged in at any given time and it
is only concurrent users that "strain" Access multiuser.
Larry Linson
Microsoft Access MVP
"Vinnie" <vinootz[ at ]comcast.net> wrote in message
news:eilu1M81GHA.4972[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] > Greeting All,
>
> Ive never had to do anything like this (Newbie).
>
> I am building a DB to conduct some Voting.
> Consists of 42 Voters.
> I have created the Tables I need for it, created the forms and split it.
> Now Im in the process of testing.
>
> Question is?
> What should the relations look like for the below basic set up? I put
> down what I bave so far.
> I dont want to run into the records being "locked", and then Error box
> pops up and says "Save Record, Drop Changes, Cancel". I think I have the
> relationships all hosed up. And I dont think Im using the primary keys
> correctly.
> But not sure. Any help would be greatly appreciated.
> Also, is 42 Frontends linked to to 1 BE too much? Not alot of data,
> mostly Scale of 1-10 Dropdown Choice Questions, or a lookup of names to
> vote for.
> I know you will most likely require a lot more info to really help me, but
> just wanted to see if something really sticks out like a sore thumb.
>
> tblSeat-PK
> tblSeatID-PK (No Dups)
> SeatNumber (No Dups)
> Name
>
> tblQuestion1
> Question1AnswerID (PK No Dups)
> SeatNumber (LookUp) One to Many
> Question1Answer
> Comments
>
> Thanks as always !
> Vincent
>
|