I'm trying to develop a basic database manager using Remoting/CF/ODBC (access).
And have a basic application working fine on a small, flat file db, allowing me
to ADD, EDIT, DELETE records. I've used textArea instances bound to the
dataset to view and enter the field data
However I now want to apply this to a much larger relational database and
include an option to edit the related tables etc. I have no problems with the
CFC SQL call, and can pull-in all the data I need into a dataset and bind it to
other components as necessary. The problem is that I now have potentially 70-80
fields related to each record and unless I instantiate ALL the textAreas on the
first frame I am unable to bind them to the dataset. This, of course is not
practicable due to the lack of space on the stage. What I'd really like to do
is have a half dozen or so frames in the movie, each one dealing with a
particular data aspect and navigate between the frames as required.
Is there a "cheat" way of binding the textAreas to the dataset from within the
movie -- i.e. almost like "refreshing" the dataset. Or is there some other way
of achieving my target. I did manage almost to do what I wanted using dynamic
text fields linked to the dataset's "currentItem" property:
e.g. z_number_txt.text = ds.currentItem.z_number;
but I couldn't manage to get the resolver to work with this to update the
database!
Baffled............................... mike
thedanster - 11 May 2004 04:17 GMT
I had a similar problem. I am on MX04. If you follow the Flash application
model instead of the old reliable flash document approach, then you can
establish your connection and dataset/resolvers and all associated code on the
main application slide/form. Then any child forms could contain your specific
entry fields. The screens(as they are referred to ) seem to resolve the first
frame problem. I suspect this is the way MM wants we user folk to develop
anyway.
DAN
Paul Whitham TMM - 11 May 2004 04:20 GMT
Have you thought about using something like an accordion pane that wya you
could include all your fields.

Signature
Regards
Paul Whitham
Macromedia Certified Professional for Dreamweaver MX2004
Valleybiz Internet Design
www.valleybiz.net
Team Macromedia Volunteer for Ultradev/Dreamweaver MX
www.macromedia.com/support/forums/team_macromedia
> I'm trying to develop a basic database manager using Remoting/CF/ODBC (access).
> And have a basic application working fine on a small, flat file db, allowing me
[quoted text clipped - 22 lines]
>
> Baffled............................... mike
weeble - 26 May 2004 11:22 GMT
Hi Dan,
Using the Application model certainly resolved this problem. It's an area I'd
not bothered looking at previously -- I think I subconciously got it in my
mind that it was there to make things easier for non AS programmers. However
this is firmly not the case, and it has a lot going for it for handling forms
and large scale data integration.
Whether or not MM is trying to steer us down this road, I'm not too sure. I
still prefer the "root" timeline working practices from a coding point of view,
and found with the screen-based model I was temped to put much more code on the
individual components, which was a habit I'd just gotten out of.
Anyway, thanks for the guidance, and my advice to anyone else on the forum who
have also "overlooked" this area of 2004 Pro to go take a peek.
Mike