Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / New Users / June 2006

Tip: Looking for answers? Try searching our database.

Form/subform strategy help needed.

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Acanthocanis - 14 Jun 2006 10:53 GMT
Ok... I have a database I've been working on extensively. I recently ran
across an issue where refreshing records causes a stack memory problem and
the program crashes. I had one main form with 5 subforms . The fifth subform
then had 3 more subforms. There are no additional forms or subforms. I have
tried creating a 'wizard' type series of forms to input the data for each
subform separately (so a smaller number of forms/subforms are open
simultaneously), but for whatever reason, I cannot get one form to pass the
linking field's data to the next form, most likely because at that point,
there are no matching records existing for any of the tables upon which the
subforms are based. For example, I've tried having FormA create records for
ParentTableA, then close FormA when finished to open FormB, which contains
the primary key from ParentTableA, then a subform for table ChildA. However,
I can find no method that opens FormB with the desired record added using
FormA. I could manually type in the linking data, but surely there is a way
to make this work automatically.
Klatuu - 14 Jun 2006 14:03 GMT
There are a couple of ways to do this.  Which you use depends on how you are
structuring your recordsets and personal preference.  Both use arguments of
the OpenForm method.  One is to use the Where argument.  It will limit the
recordset of Form B based on the Where condition.  The other is the OpenArgs
argument.  Pass Form B a value that it can use in the Load Event to point to
a specific record or to set it's filter.

> Ok... I have a database I've been working on extensively. I recently ran
> across an issue where refreshing records causes a stack memory problem and
[quoted text clipped - 11 lines]
> FormA. I could manually type in the linking data, but surely there is a way
> to make this work automatically.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.