I have a favor of the list.  Can someone who knows Access explain how to
accomplish the same type of thing by using fusebox.  
1.  In Access I would make a main form that is attached to a query.
2.  This main form would be filled with many subforms showing specific
information.  Each subform would have its own query- usually just 2 tables
so that info could be added updated.
(ie: the main form would show the client demographic info- one subform would
show spouse info- another subform would show medical history, etc/on/on) I
could have a dozen subforms on a main form.
3.  These subforms would be attached to the mainform through a
primary/foreign key combo.  This part was very easily to accomplish- it was
set in the form properties.  In the properties section I would list as the
parent/child link the id# of the primary/foreign id#.
A user would see the main form- would be able to navigate through forms with
buttons and with permission edit add info into the subforms.

I'd like someone to explain how you accomplish the same type of thing in
fusebox.  I assume this would best be done with frames.(?)
How are the pages best set with each other and to the query to show the
information. (ie: in access linking the pages with parent/child link would
do this.  So although my query for a subform may say list all the spouse
names only main form person's spouse name would show up).
I keep feeling like I understand the logic of fb, but my background and
practical experience is all in Access/sql.  
Can someone please explain the fb practicals in terms of access
forms/subforms only background.
Thanks in advance.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to