Re: Navigating on forms...

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

The Current event fires every time a different record in the form's
underlying recordset becomes active (i.e.: becomes the current record),
whereas the Update event only fires when you make a change to the data in
the current record. Therefore the Current event would be the correct one.

Putting a last visted field in the primary table would be a mistake, since
that would cause problems if you had more than one concurrent user for your
application.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"magmike" <magmike7@xxxxxxxxx> wrote in message
news:1194198890.777614.166310@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

- Or perhaps on the id field's OnUpdate? What exactly does OnCurrent
cover?

Or, perhaps - add a "lastvisited" field to the primary table, and then
the back button would resort the form based on lastvisited DESC? If
you think that's a decent idea, how would you go about updating that
field with the current date/time when the record is brought into the
form?

On Nov 4, 10:30 am, "tina" <nos...@xxxxxxxxxxx> wrote:
there's no built-in way to do it, but you could probably set up your own
system. i've never tried it, but you create a "history" table, to hold
the
form table's primary key value. then add code to the form's Current event
procedure, to write the current record's primary key value to the history
table. set your back button to do a Find where the form's primary key =
the
value in the history table.

that would give you a simple "go back one" action. with more work and
thought, you might be able to expand the history to multiple records, and
hold "x" number of records in the history table between sessions.

hth

"magmike" <magmi...@xxxxxxxxx> wrote in message

news:1194190178.716975.307690@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



Is there a way to make your form operate like a browser with a forward
& back button?

And I don't mean sequentially through the records the form is bound
through, but as far as history, or visited records per se.

For example, I do a search on my form and pull up Acme Printing
(record # 103). While looking at their record, I get a phone call from
Johnson Marine (record # 671), so I therefore go to their record on
the form. Once done with call and their record on the form, I simply
hit the "Back Button" to return to Acme Printing.



.

Relevant Pages

  • Re: Auto-generate recently visited record-list
    ... Form Company with CompanyID as primary key and autonummered / ... Table History with LogID and FkID ... Allen Browne - Microsoft MVP. ... On the company form I added a combo list CompanyName ORDER BY Inserting ...
    (comp.databases.ms-access)
  • datasets - working with alot of data
    ... But this is more of a general question. ... the oldest million records into a history table, ... I could have made a primary key out ... of this post will not scare people off from reading it. ...
    (microsoft.public.dotnet.general)
  • Re: Nested sort, trying again
    ... Users never see the primary key, only the NAMEX, ... Because history is important, locations can only become inactive, never deleted. ... ALTER TABLE IS3.LOCATIONS ...
    (comp.databases.theory)
  • Re: writing a query
    ... start_date DATETIME NOT NULL, ... PRIMARY KEY (ssn, start_date)); ... If you try to do this with just one date in the history, ...
    (microsoft.public.sqlserver.programming)
  • How get the key of a grid?
    ... I have a gridview, ... these buttons, an event fires. ... I would like to know the primary key ... but I also want that primary key row to be ...
    (microsoft.public.dotnet.framework.aspnet)