[AccessD] Recordset to a Continuous Form

Hi Gustav,

>>Yes, this is nice for a read-only application ... do these count for
90% of all frontends?

With DAO it works like a normal bound app. I agree with ADO it is
useless. I'm doing this with DAO so it serves it's purpose...

>>Yes, much more fun to deal with the links any time a form is to be
loaded. You could create a class for that ...

Only need to do this once. The app is loaded and the path automatically
stored within a text box on the main menu. Only have to read this value
when making a connection eg:

Set dbs = Opendatabase(Forms!frmMainMenu!txtAppPath)

It works quite well...

Vlad

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Thursday, 14 October 2004 1:20 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Recordset to a Continuous Form


Hi Vlad

> I liked Susan's solution as it only binds the form temporarily, while 
> the user is viewing it. Once the form is shut down, the app remains 
> totally unbound.

Yes, this is nice for a read-only application ... do these count for 90%
of all frontends?

And why bother with updating of records - users are sooo demanding!
Saves a lot of multi-user troubles as well.

> One of the advantages of this approach too is that it gives you total 
> flexibility to the path of the BE. No more refreshing the links when 
> the app is started...

Yes, much more fun to deal with the links any time a form is to be
loaded. You could create a class for that ...

/gustav

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