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 / June 2007

Tip: Looking for answers? Try searching our database.

Access 2000 .... pattern recognition

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Ondy2112 - 24 May 2007 18:23 GMT
Hi,

In Access 2003 if had a series of cells in a column that I wanted to type a
pattern of numbers into, all I had to do was hold down the down-arrow and it
would race down the column filling in my pattern.

For example, in 2003, if I typed "2", then down, then "4", then down, then
"6" then down... Access would recognize that I'm filling in those cells with
every other even number andall I'd have to do is hold the down-arrow down for
as many cells as I want to do that.

Now here in 2007, it's not doing that anymore, and I have to manually type
"2", "4", "6", "8", "10", etc. etc.  

I'm not talking about any kind of auto-number feature here, by the way,
because I only might want to do it for a certain set of rows or maybe queried
rows.

Is this something I have to turn on, or has this been completely eliminated
from 2007?  Thanks.
Pat Hartman (MVP) - 24 May 2007 18:38 GMT
This "feature" should never have been added to Access in the first place and
perhaps the A2007 team saw the light.  Access is NOT a spreadsheet and
tables are not worksheets and they do not contain cells. If you want to
number your rows, do it in a report.

To answer your question, I don't see any setting in A2003 to turn this
behavior on or off and I don't have A2007 loaded here.  If there is a
setting, it would be somewhere near spell check or auto correct.

> Hi,
>
[quoted text clipped - 22 lines]
> eliminated
> from 2007?  Thanks.
Ondy2112 - 24 May 2007 18:51 GMT
I'm not really needing it for display or reporting purposes.  It's a behind
the scenes sort order field I need to fill in for ony certain rows, and not
others, which I've queried out.

Thanks, though.

By the way, if they aren't cells, what are they?  Am I not supposed to use
Access as a data editor and only use UPDATEs and INSERTs?

> This "feature" should never have been added to Access in the first place and
> perhaps the A2007 team saw the light.  Access is NOT a spreadsheet and
[quoted text clipped - 31 lines]
> > eliminated
> > from 2007?  Thanks.
Douglas J. Steele - 24 May 2007 19:33 GMT
You're not supposed to work directly with tables (or queries). Forms are
what are intended to let you work with the data.

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

> I'm not really needing it for display or reporting purposes.  It's a
> behind
[quoted text clipped - 48 lines]
>> > eliminated
>> > from 2007?  Thanks.
Ondy2112 - 24 May 2007 19:47 GMT
Then why do they even give us a Datasheet View and/or the ability to edit
data directly, if I'm not supposed to use it?  Nobody else excpet me is using
this, I don't need a common user to enter data into the table, so I don't see
the need for the overhead of a form.

> You're not supposed to work directly with tables (or queries). Forms are
> what are intended to let you work with the data.
Bill Mosca, MS Access MVP - 24 May 2007 21:11 GMT
Ondy

If you are the only one using the database, then by all means enter data
directly into the tables. Forms are meant to guide and restrict users other
than the one doing the designing.

The "cells" you asked about are actally a combination of 2 things: the
record and the field. Think of it like time and space. Both are needed to
define a presence. Both the record and the field are needed to define a
value.

If you have a need for sequential numbering, you could do it in Excel and
then paste it into the Access table. I, for one, found that feature useful
when creating lookup tables that needed initialized sequences other than
AutoNumbers, but I am definately a minority.

Signature

Bill Mosca, MS Access MVP
http://tech.groups.yahoo.com/group/MS_Access_Professionals

> Then why do they even give us a Datasheet View and/or the ability to edit
> data directly, if I'm not supposed to use it?  Nobody else excpet me is
[quoted text clipped - 5 lines]
>> You're not supposed to work directly with tables (or queries). Forms are
>> what are intended to let you work with the data.
Tom Wickerath - 25 May 2007 00:14 GMT
isn't he using a form?

don't forms in datasheet view do the same thing?

> Ondy
>
[quoted text clipped - 21 lines]
>>> You're not supposed to work directly with tables (or queries). Forms are
>>> what are intended to let you work with the data.
'69 Camaro - 25 May 2007 00:45 GMT
Everyone please note that Aaron  Kem.pf is attempting to impersonate one of
our regular posters again.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

> isn't he using a form?
>
[quoted text clipped - 3 lines]
>>
>> If you are the only one using the database, then by all means enter data
David W. Fenton - 25 May 2007 19:43 GMT
Aaraon Kempf, masquereing as an MVP blathered in
news:enDddhlnHHA.4624@TK2MSFTNGP04.phx.gbl:

> isn't he using a form?
>
> don't forms in datasheet view do the same thing?

Yes, it's not just table views, but all datasheets.

A valid observation from Aaron! Break out the champagne!

Signature

David W. Fenton                  http://www.dfenton.com/
usenet at dfenton dot com    http://www.dfenton.com/DFA/

aaron.kempf@gmail.com - 25 Jun 2007 01:36 GMT
David

everything I say is useful

you're a MDB cry baby stop trying to discredit me

On May 25, 11:43 am, "David W. Fenton" <XXXuse...@dfenton.com.invalid>
wrote:
> Aaraon Kempf, masquereing as an MVP blathered innews:enDddhlnHHA.4624@TK2MSFTNGP04.phx.gbl:
>
[quoted text clipped - 9 lines]
> David W. Fenton                  http://www.dfenton.com/
> usenet at dfenton dot com    http://www.dfenton.com/DFA/
Tom Wickerath - 25 May 2007 00:14 GMT
bullshit

this feature IS in Access and it SHOULD BE in all future versions

> This "feature" should never have been added to Access in the first place
> and perhaps the A2007 team saw the light.  Access is NOT a spreadsheet and
[quoted text clipped - 33 lines]
>> eliminated
>> from 2007?  Thanks.
'69 Camaro - 25 May 2007 00:45 GMT
Everyone please note that Aaron  Kem.pf is attempting to impersonate one of
our regular posters again.  Tom would never post such a message.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

<SNIPPED>
> this feature IS in Access and it SHOULD BE in all future versions
>
>> This "feature" should never have been added to Access in the first place
David W. Fenton - 25 May 2007 19:42 GMT
"Pat Hartman \(MVP\)" <please no email@aol.com> wrote in
news:entGKpinHHA.5032@TK2MSFTNGP02.phx.gbl:

> This "feature" should never have been added to Access in the first
> place and perhaps the A2007 team saw the light.  Access is NOT a
> spreadsheet and tables are not worksheets and they do not contain
> cells. If you want to number your rows, do it in a report.

It's funny. The overall goal in A2K7 seems to have been to make
Access more user-friendly for casual users. I always thought that
the spreadsheet increment function introduced in A2K was there for
exactly that reason.

I agree it doesn't belong in a database, but it wouldn't be the
least useful function if it could be turned on at will for a
particular field in a datasheet (and would be off by default, of
course).

I was never terribly bothered by it, even though I edit data in
datasheets a lot (when doing data cleanup, which, it seems to me,
never ends).

Signature

David W. Fenton                  http://www.dfenton.com/
usenet at dfenton dot com    http://www.dfenton.com/DFA/

 
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.