A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Can a field name start with a number?



 
 
Thread Tools Display Modes
  #11  
Old February 1st, 2005, 01:37 PM
Jeff Boyce
external usenet poster
 
Posts: n/a
Default

Don

It sounds like you and your users do your serious work in Excel. Simply
importing Excel data, without normalization, means you won't be able to use
the built-in features and functions in Access that expect and depend on
relational data.

If this isn't a problem, no worries. But now you have me curious why you
want to import into Access, if Excel is your workhorse?

Jeff Boyce
Access MVP

"Don Wiss" wrote in message
...
Jeff Boyce -DISCARD_HYPHEN_TO_END wrote:

Is there a chance you've imported an Excel "database", using the column
names (e.g. [100xs100], [50xs50])?


My Access tables are almost always imported from an Excel worksheet. A few
are imported from comma delimited files. For my needs Access is nothing

but
a repository for Excel. Any updating is done in Excel, or in the program
that generates the CDF files, and then reimported.

I ask because it seems possible that your field names in Access include
data, which will give you headaches down stream... Since I don't know

what
your [100xs100] refers to, I'm only wondering. Another example of
fieldnames with data embedded might be [January2005], [February2005], ...


I don't know what you mean by including data. The user is selecting
insurance layers. The column headings/field names (with spaces compressed
out) match what is available in a drop down combo box.

Don donwiss at panix.com.


  #12  
Old February 1st, 2005, 04:53 PM
onedaywhen
external usenet poster
 
Posts: n/a
Default


Jeff Boyce wrote:
now you have me curious why you
want to import into Access, if Excel is your workhorse?


Excel has a 65535 (ish) row limit. A Jet database table can handle many
more rows and therefore makes for a wonderful data heap. Access...
normalization... what are they g?

Jamie.

--

  #13  
Old February 2nd, 2005, 01:36 AM
Don Wiss
external usenet poster
 
Posts: n/a
Default

Jeff Boyce -DISCARD_HYPHEN_TO_END wrote:

If this isn't a problem, no worries. But now you have me curious why you
want to import into Access, if Excel is your workhorse?


Some of the databases are quite large. Having them in the workbook would
make the workbook enormous and unwieldy.

Then one wants independence between the parameters and the user's input,
which gets saved along with the workbook. Allows existing data to use newer
parameters.

Then it seems that one can read in a record just as fast, or faster, than
doing a match to find which row on a sheet, and then reading in that row so
the macro can work on it.

Don donwiss at panix.com.
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Text Form Field Ref in Footer Won't Update on Screen StarWine General Discussion 3 December 6th, 2004 07:17 PM
query a number stored as text Lee Running & Setting Up Queries 19 October 13th, 2004 04:10 AM
Fractional Number Value in a field Maria K Using Forms 2 June 22nd, 2004 12:39 AM
increment number field [email protected] Database Design 2 April 29th, 2004 11:29 PM
Extract variable number of chars from variable start position? Ann Scharpf Worksheet Functions 9 February 25th, 2004 03:10 PM


All times are GMT +1. The time now is 02:34 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.