[AccessD] Loading more than one instance of a form

I agree.  That is why I tend to use other front ends.  The REAL drawback
with the Access GUI is how it deals with windows and class objects like
forms and reports.  They are special creatures that don't play like objects
in other environments.

Drew

-----Original Message-----
From: Kenneth Ismert [mailto:kismert at sbcglobal.net]
Sent: Monday, June 26, 2006 1:32 PM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Loading more than one instance of a form



This is a good example of a feature that's just not worth pursuing in
Access. Multiple form instances were a poorly thought-out feature in
the first place. The work-arounds you have to do to make multiple
instances work are all hacks, and ugly hacks at that. 

Do yourself a favor and restrict all Access development to single-form
instances. You can get 95% of the benefit of multiple instances at 5%
of the progamming effort. And other developers will be able to figure
out what the hell you are doing. 

Only Microsoft can make multi-instances work, and they are never going
to do it (at least, I'm not holding my breath). MS could fix this mess
if they did two things: 

1. A generic object multiple-instance creation method:

  Set rForm = Application.CreateFormInstance("myform") 

2. A built-in InstanceID property that keyed into the Forms collection:


  Form.InstanceID   ' Could be used in code below

  Function GetFormInstance(lInstanceID As Long) As Access.Form
      Set GetFormInstance = Forms(lInstanceID) 
  End Function

Until then, if you run into one of those rare situations where you
absolutely must have multiple instances, you're better off developing
it on another platform.

-Ken  

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