![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I'm trying to convert Excel spreadsheets into MS Access Database. Basically, this will be one large table from what I can see so far. And not multiple tables. *Feel free to educate me on one large table vs multiple tables and databaes if you have time. I'm having problems importing spreadsheets into the one table. *It keeps giving me errors with the column heads "Field 'abc_' *or '_abc_' doesn't exist in the destination table". Do this "_" underscore means there is a space being imported over? Thanks..a million... |
#3
| |||
| |||
|
|
I'm trying to convert Excel spreadsheets into MS Access Database. Basically, this will be one large table from what I can see so far. And not multiple tables. Feel free to educate me on one large table vs multiple tables and databaes if you have time. I'm having problems importing spreadsheets into the one table. It keeps giving me errors with the column heads "Field 'abc_' or '_abc_' doesn't exist in the destination table". Do this "_" underscore means there is a space being imported over? Thanks..a million... |
#4
| |||
| |||
|
|
On 01/02/2011 21:15:07, Ty wrote: I'm trying to convert Excel spreadsheets into MS Access Database. Basically, this will be one large table from what I can see so far. And not multiple tables. *Feel free to educate me on one large table vs multiple tables and databaes if you have time. I'm having problems importing spreadsheets into the one table. *It keeps giving me errors with the column heads "Field 'abc_' *or '_abc_' doesn't exist in the destination table". Do this "_" underscore means there is a space being imported over? Thanks..a million... Not sure why the underscores are giving a problem. Why not change the column heads and see if that works. You have not made it clear whether you are making a new table or appending data to an existing table, in which case you will need matching field names. As to the subject of mutiple tables. IMO if you have the same bit of data over about half a dozen times, then make a table for it. E.G. if you are involved with names & addresses and you have a number of people living in the same town, then have a Town table. If you have a Town table, you certainly would want a County Table, and even if you don't have a town table you may still want a County table. Whats the advantage? If you just type an adddress in, and the person lives in the town of Shrewsbury, is the county Shropshire or Salop or Salop. (with a full stop)? Doing a search for a county then becomes difficult. The only common letter is S, but so do Somerset, Staffs, Surrey & Sussex. If you use a lookup for your counties from a town form, then you can only have Salop if that is the way the name is held in the County table. And, furthermore, if you change Salop to Shropshire in the County table, every address will change to match. Phil |
![]() |
| Thread Tools | |
| Display Modes | |
| |