Access Table Analyzer

[tkaybake]

I am importing data into an Access table. When I use the wizard it wants to restructure my data files. I don't want it to, but if I cancel the wizard doesn't import my data.

I haven't used VBA so I haven't tried writing code to write my data into my table. Any other suggestions?

Tkaybake

 

[genomon]

I am importing data into an Access table

Importing from where? Text file, spreadsheet, etc.?

All I ask is a chance to prove that money can't make me happy.

 

[tkaybake]

I am importing the data from an Excel Spreadsheet.

Teresa

 

[genomon]

Not sure what you mean by "restructure"; have you drilled down to the options and advanced features in the Wizard to see if you can change formats, etc.?

All I ask is a chance to prove that money can't make me happy.

 

[fneily]

I opened an Access database, click on the Table category, clicked File and Get External Data then Import. Changed File type to Excel, selected the Excel file. That opened Import Spreadsheet Wizard. You probably have, on the last wizard screen, a check in "I would like a wizard to analyze my tabel after importing the data". Take the check out.

And why don't you want Access to restructure you spreadsheet into NORMALIZED Access tables? Access tables ARE NOT spreadsheets. They must be normalized.

 

[xlbo]

well they don;t HAVE to be normalised - only if you want a normalised data structure for maintaining the integrity of your data. If you're just importing into access to report off for example then there is little point in normalising the data...

Rgds, Geoff

We could learn a lot from crayons. Some are sharp, some are pretty and some are dull. Some have weird names and all are different colours but they all live in the same box.

Please read FAQ222-2244 before you ask a question

 

[fneily]

And that's exactly what's wrong with the world today, a bunch of nihilists running around. Instead of following a benevolent dictator known as the protocols of relational databases, if it works then do it. Watch out Access! Barbarians at the Gate!

 

[SkipVought]

Ahhhhh, yes. The perpetual pugnaciousness between the practicers of purest principles and the practiotioners of practicality.

Skip,

_{Did you hear what happened when the OO programmer lost his library?...
He's now living in OBJECT poverty!}

 

[xlbo]

OP has not informed us as to what the data will be used for post import so we can't really say either way

if only the real world was as nice and clear cut as the theory eh.....Access is not just used for maintaining transactional databases. Normalisation is not always the way to go - I agree that it is for any working database that has to be maintained but Access gets used for much more than that - manipulation of data that is too clunky for excel, one off reports, pre aggregation of reporting data - none of these things rely on relational integrity necessarily and all that normalisation achieves is more complexity on the queries and more time taken for them to run...

Rgds, Geoff

We could learn a lot from crayons. Some are sharp, some are pretty and some are dull. Some have weird names and all are different colours but they all live in the same box.

Please read FAQ222-2244 before you ask a question

 

[fneily]

more complexity on the queries and more time taken for them to run..."
Oh well, we can't have complexity(?, no duplicate data, compact tables, etc.) and we certainly don't want something to take 12 hundreds of a second longer. Of course, since excel isn't normalized, the user may try to do some analysis that the spreadsheet format won't let them accomplish and then THAT'll run forever.
The masses are always right! Dummy down!
Hip-hop and rap rule, down with symphonies.
Yo over you.
Spell check, not dictionary.
To, too, two - all the same.
Live for today, we may die tomorrow.
By the way, did tkaybake ever resolve her problem?

 

[xlbo]

whatever - if you really believe that you should normalise ANY data that ends up in a database, no matter what the purpose, feel free to do so. I'll use the time I save by not doing that in all instances to get more work done

I would imagine that your 1st response was what they needed (without the normalisation lecture)

Rgds, Geoff

We could learn a lot from crayons. Some are sharp, some are pretty and some are dull. Some have weird names and all are different colours but they all live in the same box.

Please read FAQ222-2244 before you ask a question

 

[ca8msm]

We have an Access application that takes a tab delimited file, imports it, cleans it up a bit, runs a couple of functions and spits the data back out to a cleaned up file for importing into another application. I see absolutely no reason to normalise this data.

I'm sure this situation could be applied to other uses as well.


-------------------------------------------------------

Mark,
[URL unfurl="true"]http://aspnetlibrary.com[/url]
[URL unfurl="true"]http://mdssolutions.co.uk[/url] - Delivering professional ASP.NET solutions
[URL unfurl="true"]http://weblogs.asp.net/marksmith[/url]

 

[HarleyQuinn]

Quite a few I'd imagine...

HarleyQuinn
---------------------------------
The most overlooked advantage to owning a computer is that if they foul up there's no law against wacking them around a little. - Joe Martin

Get the most out of Tek-Tips, read FAQ222-2244 before posting.

 

[tkaybake]

I did get my issue resolved by using an older version of access. The table I am creating is just a temporary table to allow me to manipulate the data and then write it into another Access table in it's final form. I really didn't see the need to normalize my temporary table, it just would have added more complexity to my processing which I really don't need. Thanks for all the advise. I may be back later for more, this is my first Access project.