By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,389 Members | 1,955 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,389 IT Pros & Developers. It's quick & easy.

Tracking Notes

P: n/a
Hi All,

I created 'Notes' table which is linked to the main 'Client' table
(One-to-many). The form which shows client details has a tabbed page
for tracking notes. I have created two subforms to enter new notes and
to view previous notes.

NewNotes - Continuous Form View, No additions allowed
NotesHistory - Single Form View, Opens Default to New Record.

Since both subforms have linked to the ClientID, they display only
records which are linked to that particular client.

When I enter notes in NewNotes and save, it is not immediately
displayed on NotesHistory form. I need to close and re-open that
record again for last notes to be updated on NotesHistory form.

Can anyone suggest me how I can update notes immediately? Also How can
we create a time stamp for each note?

May 29 '07 #1
Share this Question
Share on Google+
7 Replies


P: n/a
On 29 May 2007 04:22:11 -0700, Matuag <ma****@gmail.comwrote:

You need to .Requery the NewNotes form, probably from the
NotesHistory.AfterUpdate event.

A timestamp can be created by adding a date field (e.g. DateCreated),
and setting the default value to Now()

-Tom.

>Hi All,

I created 'Notes' table which is linked to the main 'Client' table
(One-to-many). The form which shows client details has a tabbed page
for tracking notes. I have created two subforms to enter new notes and
to view previous notes.

NewNotes - Continuous Form View, No additions allowed
NotesHistory - Single Form View, Opens Default to New Record.

Since both subforms have linked to the ClientID, they display only
records which are linked to that particular client.

When I enter notes in NewNotes and save, it is not immediately
displayed on NotesHistory form. I need to close and re-open that
record again for last notes to be updated on NotesHistory form.

Can anyone suggest me how I can update notes immediately? Also How can
we create a time stamp for each note?
May 29 '07 #2

P: n/a
On May 29, 6:35 pm, Tom van Stiphout <no.spam.tom7...@cox.netwrote:
On 29 May 2007 04:22:11 -0700, Matuag <mat...@gmail.comwrote:

You need to .Requery the NewNotes form, probably from the
NotesHistory.AfterUpdate event.

A timestamp can be created by adding a date field (e.g. DateCreated),
and setting the default value to Now()

-Tom.

Ran requery, didn't work :(

May 29 '07 #3

P: n/a

"Matuag" <ma****@gmail.comwrote in message
news:11**********************@i13g2000prf.googlegr oups.com...
On May 29, 6:35 pm, Tom van Stiphout <no.spam.tom7...@cox.netwrote:
>On 29 May 2007 04:22:11 -0700, Matuag <mat...@gmail.comwrote:

You need to .Requery the NewNotes form, probably from the
NotesHistory.AfterUpdate event.

A timestamp can be created by adding a date field (e.g. DateCreated),
and setting the default value to Now()

-Tom.


Ran requery, didn't work :(
Make sure that if you're using transactions, you close that transaction
before the requery.
May 30 '07 #4

P: n/a
>
Make sure that if you're using transactions, you close that transaction
before the requery.
Can you please explain what do you mean by transactions?

May 31 '07 #5

P: n/a

"Matuag" <ma****@gmail.comwrote in message
news:11**********************@z28g2000prd.googlegr oups.com...

Make sure that if you're using transactions, you close that transaction
before the requery.

Can you please explain what do you mean by transactions?
from the MS Access Help page:

TRANSACTION Statement
Used to initiate and conclude explicit transactions .

Syntax
Initiate a new transaction.

BEGIN TRANSACTION

Conclude a transaction by committing all work performed during the
transaction.

COMMIT [TRANSACTION | WORK]

Conclude a transaction by rolling back all work performed during the
transaction.

ROLLBACK [TRANSACTION | WORK]

Remarks
Transactions are not started automatically. To start a transaction,
you must do so explicitly using BEGIN TRANSACTION.

Transactions can be nested up to five levels deep. To start a nested
transaction, use BEGIN TRANSACTION within the context of an existing
transaction.

Transactions are not supported for linked tables.

if you don't recognize this, then it's probably not your problem.
transactions are used to insure that multiple table updates complete
normally--or are rolled back completely, so that partial updates do not
occur due to system halts, etc.

sorry if i've confused the issue with this.
Dale.
May 31 '07 #6

P: n/a

"Dale" <dhcarter_at_alliancecable_dot_netwrote in message
news:46***********************@news.mindlink.net.. .
>
"Matuag" <ma****@gmail.comwrote in message
news:11**********************@z28g2000prd.googlegr oups.com...
>
Make sure that if you're using transactions, you close that transaction
before the requery.
Can you please explain what do you mean by transactions?

from the MS Access Help page:

TRANSACTION Statement
Used to initiate and conclude explicit transactions .

Syntax
Initiate a new transaction.

BEGIN TRANSACTION

Conclude a transaction by committing all work performed during the
transaction.

COMMIT [TRANSACTION | WORK]

Conclude a transaction by rolling back all work performed during the
transaction.

ROLLBACK [TRANSACTION | WORK]

Remarks
Transactions are not started automatically. To start a transaction,
you must do so explicitly using BEGIN TRANSACTION.

Transactions can be nested up to five levels deep. To start a nested
transaction, use BEGIN TRANSACTION within the context of an existing
transaction.

Transactions are not supported for linked tables.

if you don't recognize this, then it's probably not your problem.
transactions are used to insure that multiple table updates complete
normally--or are rolled back completely, so that partial updates do not
occur due to system halts, etc.

sorry if i've confused the issue with this.
Dale.

Where did you see "Transactions are not supported for linked tables."???
I know transactions work where the BE is Jet. Access help does warn that
some databases such as Paradox do not support transaction.
May 31 '07 #7

P: n/a

"paii, Ron" <pa**@packairinc.comwrote in message
news:ZZ******************************@athenet.net. ..
>
"Dale" <dhcarter_at_alliancecable_dot_netwrote in message
news:46***********************@news.mindlink.net.. .
>>
"Matuag" <ma****@gmail.comwrote in message
news:11**********************@z28g2000prd.googleg roups.com...
>
Make sure that if you're using transactions, you close that
transaction
before the requery.

Can you please explain what do you mean by transactions?

from the MS Access Help page:

TRANSACTION Statement
Used to initiate and conclude explicit transactions .

Syntax
Initiate a new transaction.

BEGIN TRANSACTION

Conclude a transaction by committing all work performed during the
transaction.

COMMIT [TRANSACTION | WORK]

Conclude a transaction by rolling back all work performed during
the
transaction.

ROLLBACK [TRANSACTION | WORK]

Remarks
Transactions are not started automatically. To start a transaction,
you must do so explicitly using BEGIN TRANSACTION.

Transactions can be nested up to five levels deep. To start a
nested
transaction, use BEGIN TRANSACTION within the context of an existing
transaction.

Transactions are not supported for linked tables.

if you don't recognize this, then it's probably not your problem.
transactions are used to insure that multiple table updates complete
normally--or are rolled back completely, so that partial updates do not
occur due to system halts, etc.

sorry if i've confused the issue with this.
Dale.


Where did you see "Transactions are not supported for linked tables."???
I know transactions work where the BE is Jet. Access help does warn that
some databases such as Paradox do not support transaction.

yes, i was concerned by that too. i just copy/pasted the above from the MS
Access 2003 Help screen. i have also used transactions with linked MySQL
tables and they appear to work fine. The MySQL tables must be InnoDB type
because that is the only table type that supports transactions in MYSQL.
but i did not want to alter the contents of the MS Access Help text, so i
left it as it appears above.

regards,
dale.
Jun 1 '07 #8

This discussion thread is closed

Replies have been disabled for this discussion.