Re: Is Access bogus, or is it me?
- From: "jwray727" <jeff_g_wray@xxxxxxxxxxxx>
- Date: 14 Aug 2006 11:24:59 -0700
The other approach that occurred to me was to use some Excel functions
to clean it up before importing to Access. Investigate Excel functions
like TRANSPOSE that might do the trick (Disclaimer: I'm not an Excel
expert).
I need to add my to cents into the rants listed above on this topic.
Here is a valid reason for placing data in column format instead of the
normal row format:
Excel currently has a limitation of 256 columns, I currently have a
project that is required to track upto 650 data elements per unit, with
~300 units worth of data. I need to place this data into Access but
cannot perform a normal "Import from Excel" because all of my data
field names are listed in column 1, instead of row 1.
ie,
__________________________________________________________
Col1 | Col2 | Col3 | Col4 ... One Col for each Unit
SN | X | Y | Z
HiLim1| 10 | 10 | 10
LoLim1| 0 | 0 | 0
T1_250| 2 | 5 | 7
T1_300| 12 | 1 | 5
..
..
..
one row for each test element (650 rows needed)
__________________________________________________________
I cannot perform a transpose of my data as it will break the 256 column
limit.
It sure would be nice for Access to have the capability to import with
column 1 as header instead of the current capability of only row 1 as
header.
How can I do this using Access. I am a whiz in excel macro writing, but
only now starting to use Access.
.
- References:
- Is Access bogus, or is it me?
- From: DFS
- Re: Is Access bogus, or is it me?
- From: Appelq
- Re: Is Access bogus, or is it me?
- From: DFS
- Re: Is Access bogus, or is it me?
- From: Appelq
- Is Access bogus, or is it me?
- Prev by Date: Re: Unique Index
- Next by Date: list of tables in mdb file
- Previous by thread: Re: Is Access bogus, or is it me?
- Next by thread: Re: Is Access bogus, or is it me?
- Index(es):
Relevant Pages
|