display old value, enter new value

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Judy Ward - 17 Mar 2007 00:40 GMT

I'm hoping I can even explain my problem!

I have a table of SubTasks and a table of ESLOCS. I have a query
qryLatest_SubTasks (based on the latest SubTask date) and a query
qryLatest_ESLOCS (based on the latest date the ESLOCS were entered). The
record souce for my form, frmEnter_ESLOCS, is a qrySubTasks_and_ESLOCS, that
joins qryLatest_SubTasks and qryLatest_ESLOCS. The form displays bound
fields from the query in continuous forms mode.

None of the bound fields in my form are updatable, which is fine because
when they update their ESLOCS, I do not want to change the existing ESLOC, I
want to enter a new record in the table with the current date. I have no
problem with the code to do this.

My problem is giving the user a way to enter a new ESLOC. I have tried two
different tactics. One was to include an unbound text box, txtNew_ESLOC.
Even though I can see a text box for each different line of my form, an entry
in one text box populates all the other text boxes--they are not individual.
If I make txtNew_Esloc bound to a field in my query, then it is not updatable.

Any suggestions? If you know of a resource that displays data and allows
the user to enter changes in a separate field, I would appreciate knowing
about it.

Thank you,
Judy

Reply to this Message

Cheese_whiz - 18 Mar 2007 14:35 GMT

Hi Judy,

I have an unnatural disdain for continuous forms, but I do occasionally use
them anyway. Usually, when I use one, it's in a subform control...often on a
tab of it's own.

What I've done is just add a command button to "add new record" with the
on_click event of the button opening a form designed to add new records.

On the on_close event of that 'add new record' form, I requery the subform.
That way it adds the new record immediately to the subform display on my
original form.

Does that make sense? Is that a workable solution?

CW

> I'm hoping I can even explain my problem!
>
[quoted text clipped - 22 lines]
> Thank you,
> Judy

Reply to this Message

Judy Ward - 18 Mar 2007 20:31 GMT

Thank you for your response. Yes, this does make sense. I was guessing I
was going to have to resort to having another form open to enter the new
ESLOCS (and then requery the "display" form to show the new record).

With this design, the user has to click the button for each record that he
wants to change. I haven't gotten feedback from any users yet, but I am
anticipating that they are going to ask for a way to update more than one
record at a time--and I can't think of a way to do that since a text box on
the form is not unique to each record (and a bound field is not updatable).

Thank you again for responding,
Judy

> Hi Judy,
>
[quoted text clipped - 39 lines]
> > Thank you,
> > Judy

Reply to this Message