Network Problems with Access 2007

[BobW]

I am trying Access 2007 for the first time and am having trouble sharing
files between two computers on a local network. Computers A and B are
running XP and Access 2007 in 2003 mode.
The basic layout is computer A has a Access file containing queries, forms,
reports (Procedure File) in a Front End .mdb file with its tables linked to
another .mdb file (DataFile) containing the actual tables , a typical split
file situation.. These files are in a shared folder (XX) that are listed as
a trusted folder in A.
Computer B has the same setup listed in a different folder. When I run
the Procedure file in B linked to the tables in the Data File in B all is
well. I established a network link between Computer B and the shared folder
(XX) in computer A and linked the Procedure file tables in B to the tables
in the Data file in A. I made the network link a trusted source in B. I
get a Read Only response from the A tables and cannot input data to the
common data table in Computer A from computer B.
The network displays in computer B all the file names In computer A
shared folder (XX)
Somewhere there appears to be a Read Only Limit in the system. I must be
missing something in either Access 2007, the Router, or the Browser. Help
would be appreciated as the system is to be up by 1/1/09- thanks

 

[Machi]

Maybe a problem with the share permissions.
When a shared folder is created in XP, the share by default is read only.

To fix it:
-log on to the computer where the shared folder is, using any account with
administrative privileges (any account have them, if you haven't explicitly
created limited accounts), for example the account you used to create the
share.
-go to Start, Control Panel, Administrative Tools, Computer Management and
choose "Shared Folders" then "Shares"
-Double click on your share "(XX)" to view the share's Properties window
-In the "Share Permissions" tab, click on "Everyone" and check "Full
Control" (below , "Allow" column).
-In the same window, go to the "Security" tab, press "Add..." and
type"Everyone" then press "OK" to add it to the "Groups or user names" list
-Finally, on the same tab click on "Everyone" and check "Full Control"
(below , "Allow" column).

That's it !

 

[BobW]

Thanks- I am away from the computer until 12/30- will let you know how it
works

 

[a a r o n . k e m p f]

If you're trying to run MS Access over a network, you should be
advised that Jet doesn't run over half the networks in the real world
(WAN, VPN, Wireless)

You'd be best off by moving to SQL Server, because this just works
across any network.

 

[Tony Toews [MVP]]

Please ignore Aaron Kempf's posting as he is quite monomaniacal on the
subject of SQL Server and ADPs.

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[a a r o n . k e m p f]

Please ignore Tony Toews posting as he is quite monomaniacal on the
subject of Jet databases.

Even Microsoft admits that Jet is _UTTER_CRAP_.

----------------------------------------------------------------------------------------
Access, however, is not perfect. Performance degrades significantly as
the database size increases. The database is also prone to corruption.
Finally, starting with an Access database has tempted many developers
to do a dangerous thing. Sometimes a single-user application becomes
popular enough that there's a desire for it to be used by multiple
simultaneous users. The temptation is to just move the Access database
file to a network share, copy the application to multiple machines,
and let many users connect simultaneously. Access performance drops
off quickly with multiple users, and it's highly unlikely that an
application that was designed for a single user will work reliably
with concurrent users.

http://msdn.microsoft.com/en-us/library/aa730870(VS.80).aspx

 

[Tony Toews [MVP]]

Even Microsoft admits that Jet is _UTTER_CRAP_.

And that paragraph is exceedingly slanted and by someone who clearly
doesn't understand Access.

How many hours did it take you to find that paragraph?

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[a a r o n . k e m p f]

Well you're the idiot that's stuck reccomending an obsolete database.

We're not the ones that are slanted-- YOU ARE.

JET IS OBSOLETE AND IT HAS BEEN FOR A DECADE.

-Aaron