Tony Toews IT WORKS

C

Cyndi

I got it I got it - thank you for your new instructions - now can I
ask two questions

1 - my datafile.mdb is in g, I am copying it to c:\win\datafile.mdb
but what I want to open when it is done copying is
j:\accting\accting.mdb can it do this - right now it is copying the
file but then it goes to a blank access screen because all that is in
where I copy it to is files I link to from J - hope that makes sense

2 - How I envision it working is this

as I said my main file is j:\accting\acctingsys.mdb but alot of the
data is in G but to link direct to it is slow but there are multiple
changes all day long so what I want to happen is have my users use j
file and when they need up-to-date data to print reports or do calcs
they can hit a button to update the data from g to c which is where
your program comes in - can I make a button on an access form run your
program?


Again thanks - what it is doing now is great but it could be a little
better it I can do these things
 
T

Tony Toews

I got it I got it - thank you for your new instructions - now can I
ask two questions

1 - my datafile.mdb is in g, I am copying it to c:\win\datafile.mdb
but what I want to open when it is done copying is
j:\accting\accting.mdb can it do this - right now it is copying the
file but then it goes to a blank access screen because all that is in
where I copy it to is files I link to from J - hope that makes sense
Click to expand...

You want to leave the data MDB on the server. The FE goes on each
client work station and is linked to the data MDB.

You want to split the MDB into a front end containing the queries,
forms, reports, macros and modules with just the tables and
relationships. The FE is copied to each network users computer. The
FE MDB is linked to the tables in the back end MDB which resides on a
server. You make updates to the FE MDB and distribute them to the
users, likely as an MDE.

See the "Splitting your app into a front end and back end Tips" page
at http://www.granite.ab.ca/access/splitapp/ for more info.
2 - How I envision it working is this

as I said my main file is j:\accting\acctingsys.mdb but alot of the
data is in G but to link direct to it is slow
Click to expand...

This should be handled differently than you envision. You really
,really don't want to copy the data file to the workstation.

The three most common performance problems in Access 2000 or newer
are:
- LDB locking which a persistent recordset connection or an always
open bound form corrects (multiple users)
- sub datasheet Name property set to [Auto] should be [None]
- Track name AutoCorrect should be off

For more information on these, less likely causes, other tips and
links to MS KB articles visit my Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

Unfortunately I may not have access to the Internet for the next few
days but I'm sure others can help.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
C

Cyndi

Ok Thanks


Tony Toews said:
I got it I got it - thank you for your new instructions - now can I
ask two questions

1 - my datafile.mdb is in g, I am copying it to c:\win\datafile.mdb
but what I want to open when it is done copying is
j:\accting\accting.mdb can it do this - right now it is copying the
file but then it goes to a blank access screen because all that is in
where I copy it to is files I link to from J - hope that makes sense
Click to expand...

You want to leave the data MDB on the server. The FE goes on each
client work station and is linked to the data MDB.

You want to split the MDB into a front end containing the queries,
forms, reports, macros and modules with just the tables and
relationships. The FE is copied to each network users computer. The
FE MDB is linked to the tables in the back end MDB which resides on a
server. You make updates to the FE MDB and distribute them to the
users, likely as an MDE.

See the "Splitting your app into a front end and back end Tips" page
at http://www.granite.ab.ca/access/splitapp/ for more info.
2 - How I envision it working is this

as I said my main file is j:\accting\acctingsys.mdb but alot of the
data is in G but to link direct to it is slow
Click to expand...

This should be handled differently than you envision. You really
,really don't want to copy the data file to the workstation.

The three most common performance problems in Access 2000 or newer
are:
- LDB locking which a persistent recordset connection or an always
open bound form corrects (multiple users)
- sub datasheet Name property set to [Auto] should be [None]
- Track name AutoCorrect should be off

For more information on these, less likely causes, other tips and
links to MS KB articles visit my Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

Unfortunately I may not have access to the Internet for the next few
days but I'm sure others can help.

Tony
Click to expand...
 
Top