Re: Selecting records for print

From: Dirk Goldgar (dg_at_NOdataSPAMgnostics.com)
Date: 05/12/04

  • Next message: Alex Dybenko: "Re: Access 2002 - docmd.sendobject" 
    Date: Wed, 12 May 2004 02:34:16 -0400

    "Leif Eriksen" <anonymous@discussions.microsoft.com> wrote in message
    news:b10c01c436f2$43fdf980$a301280a@phx.gbl
    >[...]
    > Yes, I have read Tony's site, along with a couple of
    > articles. I did try their ideas. I mostly notice a
    > problem on a data*** refresh, or a resize of a form. I
    > have an event on a resize that adjusts the size of certain
    > parts of the form. Right now its near real time response,
    > with the link it was noticably slower. However, several
    > people have mentioned the advantages, so I think I should
    > try it again.

    Hmm, I don't recall hearing of this as a problem before. I'd have to
    have more specifics before I could even guess what's going on, or
    whether this is a bug of some sort.

    > Of course, I then have the additional
    > problem of keeping the front-end in sync with changes if
    > the front end is local. I recall someone, however, has a
    > freeware/shareware application that helps helps in syncing
    > up front end changes.

    Somewhere on Tony Toews' site there's a link to his Auto FE Updater.

    >> If you insist on using a monolithic database, you can still use a
    >> local table, by creating a temporary database file to hold this
    >> table. You could create this database (in the current user's Temp
    >> folder), and create the table in the database, in your startup code,
    >> and delete the database in code that runs when the database is
    >> closed. Creating a temporary "work" database is not difficult at all
    >> -- I have a simple class that takes care of it for me, when I need
    >> to do
    > it. Let me know
    >> if you're interested. It could get complicated in this case, because
    >> you must avoid creating a linked tabledef in the (monolithic)
    >> database, but you could dynamically set the recordsource of your
    >> form to a SQL statement that uses the IN clause to identify the work
    >> database that is the source for the SelectedRecords table.
    >>
    >
    > Yes, I'm interesting in your class. You can email me at
    > LeifEriksen AT Hotmail (I didn't want to use the standard
    > way of displaying this and take a chance of even more
    > spam).

    I'll send it along. 

    -- 
Dirk Goldgar, MS Access MVP
www.datagnostics.com
(please reply to the newsgroup)
  • Next message: Alex Dybenko: "Re: Access 2002 - docmd.sendobject"