[AccessD] On another subject - unbound forms

What do you mean?  Are you saying that you want to create an unbound version
of a continuous form?

Just a tip.  If you want to go unbound, especially if this is a project that
could start with an Access BE, and an Access FE, then move to a Web FE, with
a different BE (which, by the way, Access works beautifully as a web BE,
because when it is stored locally on the web server, it is just as fast as
SQL Server), I recommend that you develop using Classes (and collections),
to store your business processes, data retrieval/saving.  That way your
forms (or asp code for a web page) just have to interact with your classes.

Drew

-----Original Message-----
From: Jeanine Scott [mailto:jscott at mchsi.com]
Sent: Thursday, June 12, 2003 8:45 AM
To: accessd at databaseadvisors.com
Subject: [AccessD] On another subject - unbound forms



OK - don't mean to get any discussions started here as I've read quite a few
debates on this subject. However, I am looking at a process that I wrote 4
years ago and doing the "scratching my head" thing wondering if I can even
claim to have written it! Anyway, I really think with this particular
process I'd like to go unbound. However, my dilemma is this: I have to
display - as they enter records - and allow the user to process multiple
records at one time.  Does anyone have an example they wouldn't mind sharing
of a simple unbound app that would do this? I'd so much appreciate it!

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com