Adding data to work in progress

  • Thread starter Thread starter Lloyd
  • Start date Start date
L

Lloyd

I am at the point where I want a user to add more data to
my application while I continue to work on refining forms
and reports. Can I simply make a copy of the .mdb file,
let the user add data, then import all of that data and
overwrite what data is in my copy? Or is there another or
better way to accomplish my goal?

Thanks, Lloyd
 
Hi Lloyd,

The thing to do is split your database into two mdb files, a back end
containing just the data and a front end with the forms, reports and the
rest of the functionality. Access comes with a database splitter (in
Tools|Database Utilities or Tools|Add-ins depending on version). See
Help for more information.

If you and the other user are on the same network, put the back end in a
shared folder that you both can access, and a copy of the front end on
each computer, both linked to the same back end. Then you can develope
your front end while the other user enters data through theirs.

If you're not both on the same LAN, copy front end and back end to the
other machine. Then when the data has been entered, just copy the other
back end onto your machine and link the improved front end to that. You
just have to take care not to change the design of the tables and
relationships in the back end.
 
Thanks John, that was very helpful. I think splitting the
database as you suggest is exactly what I want to do.

One followup - how difficult is it to move the -be file to
a different location on the server? I am not sure where
the final location should be and don't want to create more
work for myself than necessary.

Thanks, Lloyd
-----Original Message-----
Hi Lloyd,

The thing to do is split your database into two mdb files, a back end
containing just the data and a front end with the forms, reports and the
rest of the functionality. Access comes with a database splitter (in
Tools|Database Utilities or Tools|Add-ins depending on version). See
Help for more information.

If you and the other user are on the same network, put the back end in a
shared folder that you both can access, and a copy of the front end on
each computer, both linked to the same back end. Then you can develope
your front end while the other user enters data through theirs.

If you're not both on the same LAN, copy front end and back end to the
other machine. Then when the data has been entered, just copy the other
back end onto your machine and link the improved front end to that. You
just have to take care not to change the design of the tables and
relationships in the back end.


I am at the point where I want a user to add more data to
my application while I continue to work on refining forms
and reports. Can I simply make a copy of the .mdb file,
let the user add data, then import all of that data and
overwrite what data is in my copy? Or is there another or
better way to accomplish my goal?

Thanks, Lloyd
Click to expand...

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.
Click to expand...
 
To move the back end, just make sure that no one is in the database and
move the mdb file to where you want it to be.

After that you'll need to use the Linked Table Manager in the front
end(s) to connect them to the relocated back end.

BTW, I said in my previous message
Of course you can: you just can't do it while the other person is using
the database. When you need to, open the back end directly from Access
and make the changes you need. Then open the front end. If you've
created any new tables in the back end, use File|Get External Data|Link
to make them available in the front end. Make and test any other
necessary changes (e.g. to queries, forms, reports) and then give the
other use a copy of the modified front end.

Thanks John, that was very helpful. I think splitting the
database as you suggest is exactly what I want to do.

One followup - how difficult is it to move the -be file to
a different location on the server? I am not sure where
the final location should be and don't want to create more
work for myself than necessary.

Thanks, Lloyd
-----Original Message-----
Hi Lloyd,

The thing to do is split your database into two mdb files, a back end
containing just the data and a front end with the forms, reports and the
rest of the functionality. Access comes with a database splitter (in
Tools|Database Utilities or Tools|Add-ins depending on version). See
Help for more information.

If you and the other user are on the same network, put the back end in a
shared folder that you both can access, and a copy of the front end on
each computer, both linked to the same back end. Then you can develope
your front end while the other user enters data through theirs.

If you're not both on the same LAN, copy front end and back end to the
other machine. Then when the data has been entered, just copy the other
back end onto your machine and link the improved front end to that. You
just have to take care not to change the design of the tables and
relationships in the back end.


I am at the point where I want a user to add more data to
my application while I continue to work on refining forms
and reports. Can I simply make a copy of the .mdb file,
let the user add data, then import all of that data and
overwrite what data is in my copy? Or is there another or
better way to accomplish my goal?

Thanks, Lloyd
Click to expand...

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.
Click to expand...
Click to expand...
 
Thanks John.

Can you point me to documentation about maintaining
application speed when splitting the data base. With a
unified application on the network, typical actions take 2
or 3 seconds. But when I split the database, they take 8
to 10 seconds and I think will be a frustration to users.

Don't know how much this depends on the db software
(Access97), size of the db (tiny at less than 1mb total),
application design (novice, with macros and some VB), the
network (Netware 6 I think), or the desktop OS (Win98 to
WinXP). I read that DFunctions can be very slow, but I
currently only have a hundred records in the primary
table. (The application should add only a few hundred
records a year.)

This will be a multiuser system, but my guess is that
there will be two or three primary, daily users and maybe
a dozen users who access it once or twice a week.

Any thoughts or resources appreciated.

Lloyd
-----Original Message-----
To move the back end, just make sure that no one is in the database and
move the mdb file to where you want it to be.

After that you'll need to use the Linked Table Manager in the front
end(s) to connect them to the relocated back end.

BTW, I said in my previous message
Of course you can: you just can't do it while the other person is using
the database. When you need to, open the back end directly from Access
and make the changes you need. Then open the front end. If you've
created any new tables in the back end, use File|Get External Data|Link
to make them available in the front end. Make and test any other
necessary changes (e.g. to queries, forms, reports) and then give the
other use a copy of the modified front end.

Thanks John, that was very helpful. I think splitting the
database as you suggest is exactly what I want to do.

One followup - how difficult is it to move the -be file to
a different location on the server? I am not sure where
the final location should be and don't want to create more
work for myself than necessary.

Thanks, Lloyd
-----Original Message-----
Hi Lloyd,

The thing to do is split your database into two mdb files, a back end
containing just the data and a front end with the
Click to expand...
forms,
reports and the
rest of the functionality. Access comes with a database splitter (in
Tools|Database Utilities or Tools|Add-ins depending on version). See
Help for more information.

If you and the other user are on the same network, put the back end in a
shared folder that you both can access, and a copy of
Click to expand...
the
front end on
each computer, both linked to the same back end. Then
Click to expand...
you
can develope
your front end while the other user enters data through theirs.

If you're not both on the same LAN, copy front end and back end to the
other machine. Then when the data has been entered,
Click to expand...
just
copy the other
back end onto your machine and link the improved front end to that. You
just have to take care not to change the design of the tables and
relationships in the back end.


On Fri, 24 Sep 2004 10:53:23 -0700, "Lloyd"

I am at the point where I want a user to add more data to
my application while I continue to work on refining forms
and reports. Can I simply make a copy of the .mdb file,
let the user add data, then import all of that data and
overwrite what data is in my copy? Or is there
Click to expand...
another
or
better way to accomplish my goal?

Thanks, Lloyd


--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.
Click to expand...
Click to expand...

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.
Click to expand...
 
Hi Lloyd,

I'm not a speed expert myself: I reckon that as long as it's quicker to
use the database than to walk to the filing cabinet and open the right
drawer then the users should be grateful. (For some reason they don't
all agree with me<g>). But take a look at
http://www.granite.ab.ca/access/performancefaq.htm

Thanks John.

Can you point me to documentation about maintaining
application speed when splitting the data base. With a
unified application on the network, typical actions take 2
or 3 seconds. But when I split the database, they take 8
to 10 seconds and I think will be a frustration to users.

Don't know how much this depends on the db software
(Access97), size of the db (tiny at less than 1mb total),
application design (novice, with macros and some VB), the
network (Netware 6 I think), or the desktop OS (Win98 to
WinXP). I read that DFunctions can be very slow, but I
currently only have a hundred records in the primary
table. (The application should add only a few hundred
records a year.)

This will be a multiuser system, but my guess is that
there will be two or three primary, daily users and maybe
a dozen users who access it once or twice a week.

Any thoughts or resources appreciated.

Lloyd
-----Original Message-----
To move the back end, just make sure that no one is in the database and
move the mdb file to where you want it to be.

After that you'll need to use the Linked Table Manager in the front
end(s) to connect them to the relocated back end.

BTW, I said in my previous message
You just have to take care not to change the
design of the tables and
relationships in the back end.
Click to expand...

Of course you can: you just can't do it while the other person is using
the database. When you need to, open the back end directly from Access
and make the changes you need. Then open the front end. If you've
created any new tables in the back end, use File|Get External Data|Link
to make them available in the front end. Make and test any other
necessary changes (e.g. to queries, forms, reports) and then give the
other use a copy of the modified front end.

Thanks John, that was very helpful. I think splitting the
database as you suggest is exactly what I want to do.

One followup - how difficult is it to move the -be file to
a different location on the server? I am not sure where
the final location should be and don't want to create more
work for myself than necessary.

Thanks, Lloyd

-----Original Message-----
Hi Lloyd,

The thing to do is split your database into two mdb
files, a back end
containing just the data and a front end with the forms,
reports and the
rest of the functionality. Access comes with a database
splitter (in
Tools|Database Utilities or Tools|Add-ins depending on
version). See
Help for more information.

If you and the other user are on the same network, put
the back end in a
shared folder that you both can access, and a copy of the
front end on
each computer, both linked to the same back end. Then you
can develope
your front end while the other user enters data through
theirs.

If you're not both on the same LAN, copy front end and
back end to the
other machine. Then when the data has been entered, just
copy the other
back end onto your machine and link the improved front
end to that. You
just have to take care not to change the design of the
tables and
relationships in the back end.


On Fri, 24 Sep 2004 10:53:23 -0700, "Lloyd"

I am at the point where I want a user to add more data
to
my application while I continue to work on refining
forms
and reports. Can I simply make a copy of the .mdb file,
let the user add data, then import all of that data and
overwrite what data is in my copy? Or is there another
or
better way to accomplish my goal?

Thanks, Lloyd


--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.
Click to expand...

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.
Click to expand...
Click to expand...
 
Back
Top