Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / General 2 / May 2008

Tip: Looking for answers? Try searching our database.

Table weirdness

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
kagard@gmail.com - 14 May 2008 19:11 GMT
Greetings:

I created a table with three fields: an autonumber, an integer, and a
date/time field. I set no validation rules or default values. When I
save the table and start entering data in datasheet view, it acts
strangely. If I put 2 in the integer field and press the tab key,
access puts 3 in the date field and then throws an error saying the
data is invalid. If I put a 3 in the integer field and press tab,
access puts 5 in the date field and throws the invalid data error
again. No other numbers that I've tried cause access to fill the data
field with a value. I've reproduced this behavior from scratch with a
second table. I've also compacted and repaired the db on the off
chance that access was getting confused. (I'm using Access 2002.)

This isn't a critical problem, so I'm not concerned if I get an
answer. I thought, though, that some of you might find this curious.
Anyone else encounter this anomaly? Any idea what's going on?

TIA

Keith
a a r o n . k e m p f @ g m a i l . c o m - 14 May 2008 19:29 GMT
Access is trying to help you.
This is 'by design'.

Don't let people enter stuff directly into a table.

-Aaron

On May 14, 11:11 am, "kag...@gmail.com" <kag...@gmail.com> wrote:
> Greetings:
>
[quoted text clipped - 17 lines]
>
> Keith
Jeff Boyce - 14 May 2008 20:48 GMT
I'll second Aaron K's observations on this, tables are for storing data,
forms for data entry/edit.  Don't let users work directly with the tables.

Access had a "feature" added that tries to anticipate a sequence ... if you
were working directly in a table!  The folks at Microsoft have heard about
this!

Good luck

Regards

Jeff Boyce
Microsoft Office/Access MVP

> Greetings:
>
[quoted text clipped - 17 lines]
>
> Keith
kagard@gmail.com - 14 May 2008 21:07 GMT
Hi Jeff and Aaron:

Seriously? I thought Aaron was kidding!

BTW, I'm not letting users enter data into tables. I was entering the
number of years of history to retain in the database and the date of
last archive. I didn't create a form specifically because I'm the only
one who will be entering data into the table.

So how does a 3 in the integer field producing a 5 in the date field
represent a sequence? Especially since it doesn't work with any other
numbers. Can this 'feature' be disabled?

Keith

> I'll second Aaron K's observations on this, tables are for storing data,
> forms for data entry/edit.  Don't let users work directly with the tables.
>
> Access had a "feature" added that tries to anticipate a sequence ... if you
> were working directly in a table!  The folks at Microsoft have heard about
> this!
Jeff Boyce - 14 May 2008 22:16 GMT
The "feature" cannot be disabled (AFAIK).

You'll have to either create yourself a simple dataentry form or pay special
attention when "loading" that table directly.

Regards

Jeff Boyce
Microsoft Office/Access MVP

> Hi Jeff and Aaron:
>
[quoted text clipped - 20 lines]
>> about
>> this!
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.