Re: database object keeps dissapearing

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Michael (x)
Date: 08/18/04 

Date: Wed, 18 Aug 2004 20:03:44 +0200

Nope... it's impractical

"MacDermott" <macdermott@NoSpam.com> wrote in message
news:OqWoZyLhEHA.3664@TK2MSFTNGP12.phx.gbl...
> How about using a combobox instead of buttons?
>
> - Turtle
>
> "Michael" <x> wrote in message news:412277a7.0@news1.mweb.co.za...
> > I hear what you're saying.
> >
> > OK, maybe my whole approach is wrong. Maybe I can pose this question
then
> >
> > I'm trying to create a "Point of Sale" system. It needs groups of PLU
> > buttons (Price Lookup). A group will be called "Breakfasts" and the
PLU's
> > will be called "Eggs & Bacon", "Farmhouse special" etc.
> >
> > So I have a form, with a tab control where each tab is a group, and then
> on
> > the particular page, a series of buttons that are the PLU's. I chose the
> > approach of designing the form on the fly because I'll never know how
many
> > PLU's have been defined in the admin section of the database.
> >
> > I could have a form with say 10 pages, and then each page has the
capacity
> > for say, 10 PLU's, but it strikes me as inefficient, and potentially a
> > memory overhead. Maybe I'm wrong.
> >
> >
> >
> >
> >
> >
> >
> >
> > "MacDermott" <macdermott@NoSpam.com> wrote in message
> > news:uOW4HiJhEHA.904@TK2MSFTNGP09.phx.gbl...
> > > I certainly don't have that level of insight into the inner workings
of
> > VBA,
> > > but it doesn't surprise me at all that code created and compiled "on
the
> > > fly" is not aware of globals set outside of it.
> > > Especially in Access, it's rarely a good idea to build an entire new
> form,
> > > or even add controls in code.
> > > The preferred method is generally to keep things invisible until
you
> > > need them.
> > >
> > > When you add the code module to your new form, do you put Option
> Explicit
> > at
> > > the top?
> > > Another thing you might try would be to precede your reference to the
> > global
> > > variable by the name of the module where it's declared, i.e. use
> > > MyModule.db
> > > instead of just
> > > db
> > >
> > > HTH
> > > - Turtle
> >
> >
>
>

Quantcast