Need some advice please!

[Nalaka Hendawitharana]

Hi,

I'm new to Access VBA, but familiar with Excel VBA. Can some one advice
me on the following please ...


* How do I create a central database where multiple users could
access it simultaneously?
* What are sites I could get more help on Access?
* What are the best Access 2000 user, developer reference books, and
way do you suggest them?

Thanks & Regards,
Nalaka

 

[Dirk Goldgar]

Answers inline.

Hi,

I'm new to Access VBA, but familiar with Excel VBA. Can some one
advice me on the following please ...

* How do I create a central database where multiple users could
access it simultaneously?

This functionality is built into Access; you don't need to do anything
special to make it work. However, to avoid corruption of the database
that may sometimes occur due to network glitches, you should actually
set up a "split" database, consisting of a "back-end" database on your
network server, containing only the tables you want to share, and a
"front-end" database containing the stored queries, forms, reports, and
modules -- that is, all the user-interface elements -- with tables
linked to the tables in the back-end database. Give each user his own
copy of the front-end, stored on his own workstation. Then only the
data will need to be brought across the network as your users work in
their front-ends.

Depending on the volume of data and the speed of your network, you may
or may not need to make changes in your application design to minimize
the volume of data that needs to be brought across the network at any
one time.

* What are sites I could get more help on Access?

www.mvps.org/access

http://www.granite.ab.ca/accsmstr.htm

http://users.bigpond.net.au/abrowne1/tips.html

These are just a few, and each has lots of links to other sites.

* What are the best Access 2000 user, developer reference books,
and way do you suggest them?

For developers, no question: the _Access 2000 Developer's Handbook_, by
(I think) Litwin, Getz, and Gilbert, from Sybex. It's clearly written,
comprehensive, educational, and chock-full of useful examples and code
routines on CD.

 

[Nalaka Hendawitharana]

Thanks a lot for your advice, Dirk ...

Answers inline.



This functionality is built into Access; you don't need to do anything
special to make it work. However, to avoid corruption of the database
that may sometimes occur due to network glitches, you should actually
set up a "split" database, consisting of a "back-end" database on your
network server, containing only the tables you want to share, and a
"front-end" database containing the stored queries, forms, reports, and
modules -- that is, all the user-interface elements -- with tables
linked to the tables in the back-end database. Give each user his own
copy of the front-end, stored on his own workstation. Then only the
data will need to be brought across the network as your users work in
their front-ends.

Depending on the volume of data and the speed of your network, you may
or may not need to make changes in your application design to minimize
the volume of data that needs to be brought across the network at any
one time.


www.mvps.org/access

http://www.granite.ab.ca/accsmstr.htm

http://users.bigpond.net.au/abrowne1/tips.html

These are just a few, and each has lots of links to other sites.


For developers, no question: the _Access 2000 Developer's Handbook_, by
(I think) Litwin, Getz, and Gilbert, from Sybex. It's clearly written,
comprehensive, educational, and chock-full of useful examples and code
routines on CD.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)