C
chris23892 via AccessMonster.com
Hello, everyone! I'm starting on a great quest here. I'll start by explaining
the big picture, then break it down to baby steps.
Big Picture-
First, I work in a lab where I test warranty returns for a product. We used
to track all this information in a spreadsheet for eack product. We got
bigger and this got overwhelming.
Last year, we migrated to MS Access. So now, I enter all my data into one
form for all products. This database is now HUGE. We have up to 5 people (and
testers) with access open for this one .mdb file while others are looking at
tables on the back end. It's slow, sluggish and we are starting to see
corruption now up two twice a month.
Time to take the database to the next level.
What's is coming up-
The next year or so, I will be having many new products plus the old ones
that are going to require all kinds of good information logged. Volumes will
be mind blowing. This current method will not support me.
What I'm thinking of-
We have data analysists that will still want to use access. That's cool, I
understand that. Why can't I have a remote database on a server where I can
pipe all my product information too? I can then have all this massive
information stored that people can link to to pull the information they need.
No interruptions with the dataflow on my end (most of this information is
going by the way of automation to increase speed).
That is where I am thinking of going.
Baby steps-------
So what is the best way to go about this? .ASP, SQL. I'm really confused, I
have visual Studio in the lab and there seems like a dozen ways I can go
about this. All are complicated and confusing. I"m great at learning and with
research, so I'm hoping to get a clear, defined direction here and see what I
can go learn.
This will be a great quest. Very cool stuff. Thanks in advance
the big picture, then break it down to baby steps.
Big Picture-
First, I work in a lab where I test warranty returns for a product. We used
to track all this information in a spreadsheet for eack product. We got
bigger and this got overwhelming.
Last year, we migrated to MS Access. So now, I enter all my data into one
form for all products. This database is now HUGE. We have up to 5 people (and
testers) with access open for this one .mdb file while others are looking at
tables on the back end. It's slow, sluggish and we are starting to see
corruption now up two twice a month.
Time to take the database to the next level.
What's is coming up-
The next year or so, I will be having many new products plus the old ones
that are going to require all kinds of good information logged. Volumes will
be mind blowing. This current method will not support me.
What I'm thinking of-
We have data analysists that will still want to use access. That's cool, I
understand that. Why can't I have a remote database on a server where I can
pipe all my product information too? I can then have all this massive
information stored that people can link to to pull the information they need.
No interruptions with the dataflow on my end (most of this information is
going by the way of automation to increase speed).
That is where I am thinking of going.
Baby steps-------
So what is the best way to go about this? .ASP, SQL. I'm really confused, I
have visual Studio in the lab and there seems like a dozen ways I can go
about this. All are complicated and confusing. I"m great at learning and with
research, so I'm hoping to get a clear, defined direction here and see what I
can go learn.
This will be a great quest. Very cool stuff. Thanks in advance