Re: One-to-one primary data synchronization

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: PC Datasheet (spam_at_nospam.spam)
Date: 02/10/04 

Date: Tue, 10 Feb 2004 02:10:18 GMT

When your data is related one-to-one, unless a set of the data needs to be kept
isolated for some reason such as sensitive personnel information, all your data
should be in one table. I sense you truly do not need tblCoSub and feel that all
the data you have in that table should more correctly be in TblSub. It sounds
like you separated the CoSub data out due to a perceived lack of screen
realestate for all the Sub and CoSub data.

What I see working nicely for you is a tabcontrol that allows you to group your
data in sets on various tabs. You could use a tabcontrol with tabs so you click
on a tab to go to a set of data or you could use a tabless tabcontrol and
activate the pages with command buttons, option buttons or radio buttons. The
latter gives a very slick appearance where the pages popup like subforms. 

--
                                         PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
                              resource@pcdatasheet.com
                                 www.pcdatasheet.com
"Jody" <anonymous@discussions.microsoft.com> wrote in message
news:3DE65B04-FE81-4C3B-9240-0B4FE4D58C00@microsoft.com...
> Hello all,
>
> I have a one-to-one relationship between the (primary) SubcriberID field
(Autonumber datatype) in tblSub and the (primary) CoSubscriberID field (number
datatype) in tblCoSub.  I have set up a main form with an embedded subform based
on this relationship, but I'd really like to have a linked form (via a command
button), while still enjoying the autonumber/number sychronization described
below.
>
> When data is added to the main form, not only does the Subscriber autonumber
field populate automatically in the main form, but the SAME number automatically
populates in the CoSubscriberID (number) field as a result of the subform
linkage and the fact that SubscriberID is driving CoSubscriberID.  This
sychronization happens automatically in an embedded situation - a very nice
feature indeed.
>
> However, In the interest of screen real estate, I would like to have the
"subform" pop-up (perhaps after pressing a command button), but still inherit
the current number from the main form (autonumber field).
>
> Does anyone know how I can essentially duplicate the sychronization effect
with a pop-up form?
>
> Most appreciated,
> Jody
>

Relevant Pages

  • Re: One-to-one primary data synchronization
    ... You could use a tabcontrol with tabs so you click ... I have set up a main form with an embedded subform based ... >> When data is added to the main form, not only does the Subscriber autonumber ... populates in the CoSubscriberID field as a result of the subform ...
    (microsoft.public.access.formscoding)
  • Re: Edit multiple tables with one form per record
    ... data for a store. ... the above is a bit unnecessary but sometimes you want to check for a record that contains the same info but the AUTONUMBER does not match the current autonumber field. ... I'd have a subform that would list the data for the store/date selected in the main form. ... Private Sub SetFilter ...
    (comp.databases.ms-access)
  • Re: Fetch the Record Number to display on the form
    ... as my form consists of a subform embedded within a form. ... So to put an autonumber field in the table corresponding to the subform ... Dave ... >>I can't find out how to do it after searching the online help, ...
    (microsoft.public.access.formscoding)
  • Re: Form to Report Question
    ... >>I have an Input form that includes data from a subform. ... >>tablescrables and is out of order on the report. ... >>number that is an autonumber field. ... >>The first five may be ingredients for the main item and the second ...
    (microsoft.public.access.forms)
  • Code to force SQL to save a record
    ... I have an Access 2000 front-end connected to a SQL 2000 backend ... I have a form with a subform ... The autonumber is not generated until the record is saved/updated in SQL ... How do I force a record to be saved so that the autonumber field will ...
    (microsoft.public.access.modulesdaovba)