DataBase - Access XP and Access 2003 sharing a system.mdw file
Asked By Elson Markwic
15-Aug-07 07:32 PM
Hi,
We run a 3rd party application here built on Access XP. The same mde file
will run under Access 2003, with one problem. It's a secured multiuser app,
so there is a system.mdw file on a Novell file server. We are an organistion
with a number of sites, and each site has it's own Novell server, with it's
own system.mdw file.
Here's the problem. On some of the servers, once an Access 2003 client has
logged in to the system.mdw file, no Access XP clients can log in. The error
message is "Microsoft Access couldn't find file '.....\system.mdw'. This file
is required for startup." The thing of it is that the file is there. Any
other application can open the file (eg, LDBView. Also, the system.mdw file
can be opened in Visual Basic with DAO, or a straight FileOpen call). As long
as another application keeps the file open, Access XP is happy and will log
in ok.
Has anybody ever seen this, or have a clue about resolving it?
Cheers, Elson
Access 2003
(1)
XP
(1)
FileOpen
(1)
Markwick
(1)
Novell
(1)
E5893BC48A99
(1)
Paths
(1)
Mdw
(1)
Joan Wild replied...
It's possible that the users don't *all* have create permission on the =
folder where the mdw is located. That is needed so that the ldb file =
can be created. =20
If users are opening via a desktop shortcut, double-check the target - =
it's possible that one of the paths is wrong.
--=20
Joan Wild
Microsoft Access MVP
file=20
app,=20
organistion=20
it's=20
has=20
error=20
This file=20
Any=20
file=20
As long=20
will log=20
Roger Jennings on Access / Sharepoint DataBase http: / / www.quepublishing.com / articles / article.aspx?p = 1606238 I was very dismayed is it makes it pretty clear that in-house hosting of your Sharepoint server with Access Services to support browser-based Access apps is something only large companies will be able to afford, because the pricing and licensing for the Enterprise version is very, very steep. The alternative is hosted Sharepoint / Access Services, and the costs do not seem terribly high. It seems to me that the pricing is upside-down. Big enterprises do not want to deploy Access apps in the browser - - they will build their own .NET apps, browser-based or not 2010, it could vastly increase those costs for organizations with legacy hardware). The features of Access 2010 used in conjunction with Sharepoint 2010 seem to me to be most compelling for and small businesses. I do not know if I could sell clients on hosted Sharepoint / Access. I have been able to sell clients on hosted Exchange, and it is been very W. Fenton http: / / www.dfenton.com / contact via website only http: / / www.dfenton.com / DFA / Access Discussions SQL Express (1) SQL Server (1) MySQL (1) Exchange Server (1) Windows Server (1
Access 2010 for software development DataBase Hi, What do I need to use Access 2010 (or perhaps 2007) to port our 2003 application and create an executable (MDE in Access 2003)? Are there any issues with 2010? -paulw Access Discussions SQL Server (1) SharePoint (1) Albert D. Kallal (1) Office 2007 (1) Office 2003 (1) Access 2007 (1) Access 2010 (1) Access 2003 (1) You can use Access 2010 to develop
deployment issues of Access XP, Access 2003, and Access 2003 DataBase On my advice, a long time ago, a customer purchased the Access XP developer edition. That special Office XP version of Access was supposed to allow the Access
Considerations migrating from Access 97 mdb to Access 2003 (or up)? DataBase What are the things I need to watch for? I know about sheet properties and Sandboxing mode and making sure to run Jet 4.0 SP8 for 2003 but what else should I look for? We're kind of at the end of the road (so it seems) with Access 97. It does not play well with Windows 7 Professional even in XP Mode, the application is crashy / unsreponsive at times. I figure moving up to a more 'modern' version of Access can help alleviate some of these problems and allow it to run native in Windows 7 rather than through the virtual XP mode. So I am all ears for recommendations on migration or ways to get Access
Access 2010 with Sharepoint 2010 DataBase I found this article http: / / sharepointproconnections.com / Articles / tabid / 149 to me was these two points: client." Hopefully this means you can test out the Access 2010 in a browser capabilities. 2.0 AA compliance. Level 1 browsers, which support 100 on other platforms. Level 2 browsers will have some limitations in rendering and behavior." Bob Access Discussions SQL Server (1) MySQL (1) Visual Basic for Applications (1) SharePoint (1) Access 2007 (1) Access 2010 (1) Office 2003 (1) Windows 7 (1) Well, the question is do you really need to go to now we build applications to the office standard (that might use outlook, excel, and MS access on the desktop), in the future we build applications that does all the similar functions figure out what is not going to work as well in the browser as in Access itself? Surely you are not claiming that 100% of an Access app is going to