I'm being a bit thick I think....

	Home Register Search Help Login

Sponsors

Shopping Cart Software
Ecommerce software integrated into Frontpage, Dreamweaver and Golive templates. No monthly fees and available in ASP and PHP versions.

Website Templates
We also have a wide selection of Dreamweaver, Expression Web and Frontpage templates as well as webmaster tools and CSS layouts.

Frontpage website templates
Creative Website Templates for FrontPage, Dreamweaver, Flash, SwishMax

Search Forums

Recent Posts

Todays Posts
Most Active posts
Posts since last visit
My Recent Posts
Mark posts read

I'm being a bit thick I think....

View related threads: (in this forum | in all forums)

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> Web Development >> ASP and Database >> I'm being a bit thick I think....

Page: [1]

Stuart at Cherry

Posts: 121
From: Leeds, West Yorkshire, UK
Status: offline

I'm being a bit thick I think.... - 4/2/2001 20:55:00

I've got my spooky login, and my back end MSAcces DB and my asp pages interacting with it. Wicked. But this question is a bit of a newbie one on MS Access. I'm trying to get every update to my DB posted from the web automatically time stamped on the DB. I thought I could just put in a field that wasn't updated from the web with a =now() in the properties. Unfortunately, if I do that - because I have an auto ID field - it creates a new field one ahead of what's been posted. So it effectively marks each record with a time that relates to the last record!

It's driving me mad.

Any suggestions?

Thanks in advance...

------------------
***born to be wild***


Spooky Posts: 26606 Joined: 11/11/1998 From: Middle Earth Status: offline	RE: I'm being a bit thick I think.... - 4/2/2001 20:05:00 Im not entirely sure what you mean. Care to expand slightly? (in reply to Stuart at Cherry)

Stuart at Cherry

Posts: 121
From: Leeds, West Yorkshire, UK
Status: offline

RE: I'm being a bit thick I think.... - 4/3/2001 20:35:00

Sure. In the design view of my access table I have put in an autonumber in the first column. In the Date_stamp column I have put the defaultvalue =now().

However, when you look at the table and you have put some records in, over in the left hand column, there is (AutoNumber) in the next record (ie the row after the last record I inputted) and over in the timestamp field there is a timestamp, done after the last record was input.

So when the next record is input, the timestamp is still what it was at the time the last record was input. And there appears another timestamp in the next row. Ie the next empty one.

This make any sense?

(in reply to Stuart at Cherry)

Vince from Spain

Posts: 658
From: Madrid Spain
Status: offline

RE: I'm being a bit thick I think.... - 4/3/2001 20:57:00

Hi Stuart,
I think I see what you mean. You have the access DB opened in Access, and you're trying to enter records manually no? Sure, if that is the case, the timastamp field is set for the next record. However, try closing the table and opening it again. Now it should be updated to the current time this "next" record no? Also, when you use this db in the web it should behave as expected.

All the best

Vince

------------------
Internet Business Solutions S.L.(Spain)

(in reply to Stuart at Cherry)

Stuart at Cherry

Posts: 121
From: Leeds, West Yorkshire, UK
Status: offline

RE: I'm being a bit thick I think.... - 4/4/2001 23:06:00

Vince, thanks. You're absolutely right.

Excellent. That's cracked it. Nice one.

Regards

(in reply to Stuart at Cherry)