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

timestamp conundrum

P: n/a
I was under the impression from the manual that if you added a field to a
table of type timestamp this would automatically be updated after each
insert/update of a new record, but all I get is 00000000.

Is there something else I should set?

Thanks.
Jul 19 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
That should work. It only will update the "FIRST" timestamp (so if you have
more than one, check the first one).
Also it can't be type time,date, or datetime, but must be type timestamp,
preferably for max compatiblity, timestamp(14).
dp

"Bill" <no@where.com> wrote in message
news:bl**********@sparta.btinternet.com...
I was under the impression from the manual that if you added a field to a
table of type timestamp this would automatically be updated after each
insert/update of a new record, but all I get is 00000000.

Is there something else I should set?

Thanks.

Jul 19 '05 #2

P: n/a
That should work. It only will update the "FIRST" timestamp (so if you have
more than one, check the first one).
Also it can't be type time,date, or datetime, but must be type timestamp,
preferably for max compatiblity, timestamp(14).
dp

"Bill" <no@where.com> wrote in message
news:bl**********@sparta.btinternet.com...
I was under the impression from the manual that if you added a field to a
table of type timestamp this would automatically be updated after each
insert/update of a new record, but all I get is 00000000.

Is there something else I should set?

Thanks.

Jul 19 '05 #3

P: n/a

"D. Pickering" <dc*****@hps.com> wrote in message
news:x3*********************@newssvr30.news.prodig y.com...
That should work. It only will update the "FIRST" timestamp (so if you have more than one, check the first one).
Also it can't be type time,date, or datetime, but must be type timestamp,
preferably for max compatiblity, timestamp(14).
dp
Thanks for replying!

Actually, I did only have one timestamp field but as I said it alwasy set a
value of 00000, so I just ended up making it a Date field instead and
setting it manually. Might work better when I upgrade to version 4.0.15.


"Bill" <no@where.com> wrote in message
news:bl**********@sparta.btinternet.com...
I was under the impression from the manual that if you added a field to a table of type timestamp this would automatically be updated after each
insert/update of a new record, but all I get is 00000000.

Is there something else I should set?

Thanks.


Jul 19 '05 #4

P: n/a

"D. Pickering" <dc*****@hps.com> wrote in message
news:x3*********************@newssvr30.news.prodig y.com...
That should work. It only will update the "FIRST" timestamp (so if you have more than one, check the first one).
Also it can't be type time,date, or datetime, but must be type timestamp,
preferably for max compatiblity, timestamp(14).
dp
Thanks for replying!

Actually, I did only have one timestamp field but as I said it alwasy set a
value of 00000, so I just ended up making it a Date field instead and
setting it manually. Might work better when I upgrade to version 4.0.15.


"Bill" <no@where.com> wrote in message
news:bl**********@sparta.btinternet.com...
I was under the impression from the manual that if you added a field to a table of type timestamp this would automatically be updated after each
insert/update of a new record, but all I get is 00000000.

Is there something else I should set?

Thanks.


Jul 19 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.