L
leavandor
I have been working at my company for over a year now using a 6 year
old Access system. We are a Roll-Wrap Manufacturing Warehouse (we make
paper that covers other non consumer paper, the huge 3 ton rolls).
Currently I'm in the process of migrating the entire system into a
single file (was about four seaparate MDBs, all of which were closely
tied to one another) and putting the data on an MSDE server.
First, I'd like to know if anyone agrees that the above is a good move.
Consolidating the forms/reports into one adp file, and having them all
reference the same MSDE DB.
Second, I'm currently stuck on a problem I'm having with trying to get
one of these old forms to do what I want. The form itself is your
standard entry type deal, and its there to record the intricate details
of our finished product that our accounting system cannot. Basically,
you enter a Parent Roll ID first and then enter anywhere from 1-3 Child
Rolls that the original was made into.
Each child roll has 10 fields of information. The way the database
currently handles this task is by having 30 different fields in the
same table, 10 for each of the three possible rolls. Now, this is as
you can see, a bit redunandant for what it needs to be. What I want to
do to is use something similar to the form we currently have, but each
of the three child rolls goes into its own database.
Now, I've looked into just simply creating self-validating code that
would UPDATE any new child rolls table with however many were made from
the parent. But knowing my coding skills, I would be able to do it but
there would be something I would forget that would later cause problems
later on. Maybe not, I haven't gone that far yet, but you know the
deal.
Regardless, I was curious if anyone else had done something like this
before. I've tried nested forms inside the form, but it doesn't work
out too well considering that each of the three nested forms would be
calling onto the same database. That, and the fact that those who use
the form are addicted to being able to copy/paste the last record for
less data entry, and you can't do that with nested forms.
Thanks in advance for any help, and please shoot any clarification
questions my way, I can suck at explaining things properly.
old Access system. We are a Roll-Wrap Manufacturing Warehouse (we make
paper that covers other non consumer paper, the huge 3 ton rolls).
Currently I'm in the process of migrating the entire system into a
single file (was about four seaparate MDBs, all of which were closely
tied to one another) and putting the data on an MSDE server.
First, I'd like to know if anyone agrees that the above is a good move.
Consolidating the forms/reports into one adp file, and having them all
reference the same MSDE DB.
Second, I'm currently stuck on a problem I'm having with trying to get
one of these old forms to do what I want. The form itself is your
standard entry type deal, and its there to record the intricate details
of our finished product that our accounting system cannot. Basically,
you enter a Parent Roll ID first and then enter anywhere from 1-3 Child
Rolls that the original was made into.
Each child roll has 10 fields of information. The way the database
currently handles this task is by having 30 different fields in the
same table, 10 for each of the three possible rolls. Now, this is as
you can see, a bit redunandant for what it needs to be. What I want to
do to is use something similar to the form we currently have, but each
of the three child rolls goes into its own database.
Now, I've looked into just simply creating self-validating code that
would UPDATE any new child rolls table with however many were made from
the parent. But knowing my coding skills, I would be able to do it but
there would be something I would forget that would later cause problems
later on. Maybe not, I haven't gone that far yet, but you know the
deal.
Regardless, I was curious if anyone else had done something like this
before. I've tried nested forms inside the form, but it doesn't work
out too well considering that each of the three nested forms would be
calling onto the same database. That, and the fact that those who use
the form are addicted to being able to copy/paste the last record for
less data entry, and you can't do that with nested forms.
Thanks in advance for any help, and please shoot any clarification
questions my way, I can suck at explaining things properly.