Need advise!

Hi,

I'm working on an access database. I need to put some values of measurement points into the database (every day 25-50 centers send these measurement points to us) It are about 50 floating point numbers. Some of the values are related to each other. Now I've got in my database 21 related numbers saved as a string, 10 related numbers saved as a string, ... But I also need to do calculations on them and I need to send them to a graph and a grid, ... For that I always have to extract them out of the strings.

Question : Is there a better way?

 Like : Save all values to database as floating points
         (Better? More place on harddisk?)

        Is there another type which is usefull?
          > Easy to handle a collection of numbers
          > Quick for display and 'real-time'

        Perhaps in future other handlings with data?
          > So is it the best to write them as numbers?        

Thanks in advance.
         

LVL 8
ZifNabAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

tecbuilderCommented:
As I see it you have to parse the information from the string in order to use regardless of what you do.  Therefore, your options become more dependant on time it takes to parse the string each time you want to use the data in the string and the space to maintain a table with all the values parsed from the string.

I don't like the notion of parsing all the time in order to use the data and in the end this method may cost more in disk space.  This method would also require you to incorporate in all programs a function to parse the data.  But what happens if something changes later on like the character that seperates the data.  You would have to rebuild each program with the new change.  Ouch!

My preference, is to break the data into a table as you recieve the data.  Use 1 or 2 columns for the primary keys and the last column for the data.  You can then build a relational database around this if you need to.  You can query the information quickly, summarize the data, etc.  All in all the best choice.

If I didn't cover something specific enough let me know.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ZifNabAuthor Commented:
Hi tecBuilder,

Thanks! I already did this yesterday. Because of you, I know I made the right decision.

Regards.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Delphi

From novice to tech pro — start learning today.