[AccessD] Recordset to a Continuous Form

Well, you could have it both ways -- just create the right recordset. ;) I
find myself using the Recordset property more and more. 

I have to ask though, why is bound a problem?????????

AHAHAHAHAAHAHAHAHAHHHHHAAH <sorry>

Susan H. 

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...