"network configuration" can mean so many things. What do you mean by it?
For example, some folks consider a Wide Area Network (WAN) to be a network
(?!) But Access front-end and back-end configuration doesn't work well over
a WAN.
On a fast, stable Local Area Network, use a "split" database - a shared
backend containing nothing but tables, and each user with a frontend
containing the forms, reports, queries etc. See http://www.granite.ab.ca/access/splitapp.htm for a detailed overview.
On a wide area (remote) network, you may need to use a terminal server
application such as Windows Terminal Server or Citrix - Access doesn't "play
nice" over a WAN. Alternatively you could store the data in SQL/Server and
revise your database to link to the SQL tables. There's a page on Tony's
website above about issues with upsizing to SQL.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
