There are posts elsewhere on this forum about the adjustments you can make to Access to improve its performance on a wireless network, i.e. make sure you have XP SP2 and not an earlier version of XP, but the fact is that no programme will perform well on a network if the network isn't performing well. Here are a few things I've learned (the hard way!)
- Use USB wireless adapters, not card type adapters. One of the prime rules of wireless networking is to keep your adapter - and your Router - away from electrical equipment and metal objects, so why anyone even makes card adapters is beyond me.
- Place your adapters/Router as high as possible (above head height is best) using a USB extension lead for the adapters if necessary. Do not put them on or near metal filing cabinets!
- Think about line of sight when placing your equipment. If your Router and an adaptor are just on either side of a wall , opposite each other, the signal may only have to pass through, say, 6 inches of wall. If they are at opposite ends of their respective rooms, however, it may have to pass through several feet of the same wall!
-If there are other wireless systems nearby using the same channel as yours, change yours to a different channel even if the other signal is weaker than yours. Remember that you need to be 5 channels away from anyone else before there is 0% overlap in the frequencies. If you cannot achieve this because there are too many nearby networks, any difference is better than none.
I have a 9 user (each in a separate room) p2p network in my office running a split Access 2000 db. The place looks a bit odd with USB adapters stuck high up on the walls but it works. Only one user has the occasional hanging problem (about once a week) but she's using an oldish laptop with only 256k of RAM and it has to run Norton Internet Security at the same time. Three of the users have the db open more or less constantly, the rest have no problem or speed issues getting in whenever they wish.
Nearly forgot, our Wireless system is standard 802.11g. max distance from an adapter to the router is about 80 feet.
Sorry if any of the above is stating the obvious, thought it might help.
Hi guys, does anyone know if there are issues using Acess on a wireless network? There seems to be problems access the database now that this has been installed... Lots of reboots required etc...
I have completed a database for a company with 60 000 clients and over 100 000 job records.
The database works at very resonable speeds on the Server computer, or the computer on which I installed the back end of the database.
Each of the other 3 computers on the wireless network, have a local copy of the Front End on their machine, and reference the Back End (BE) on the server computer.
Each of the Client computers have varing speeds when accessing the BE, some as slow as 10 minutes for a simple search, filter or just loading a form.
What can I do to improve performance across the network?
Do I need to install additional components on the other computers to improve the db performance?
I found a somewhat related thread but thought I would post a new one just in case my problem happens to others who were 'forced' to "upgrade" to Windows Vista Home Basic when buying a new machine....
Okay, no more complaining, here's the issue:
I have a small (8 MB) Access 2007 database stored on a machine in the office which is running Windows Vista Home Premium. There are two other machines running Windows XP Home (SP2) that can connect to the Access 2007 database with no issues.
But on my Dell Inspiron Vista Home Basic machine, I cannot successfully open the database stored on the Home Premium machine. I CAN see this database, I can see other files and open/copy them, but I cannot open the database. I am attempting to do this using the wireless connection.
I tried running these two commands as the administrator (found on another forum) because I think this is more of a network problem rather than an Access 2007 problem specific to Windows Vista Home Basic
netsh interface tcp set global rss=disabled netsh interface tcp set global autotuninglevel=disabled
But these two commands did nothing.
I should also point out that when this database is stored on an XP machine (one of the others in the office) the database opens just fine on this Vista Basic machine!
I'm confused and frustrated! Any help is very much appreciated.
Does anyone have any experience with placing a multi-user back-end access database on one of these inexpensive "external network hard drives"?
I have a situation where I'd like to share my database with multiple users, but the corporate IM rats have pretty much eliminated all means of allowing us lowly employees of doing that with their network. We have no file server. We do have sharepoint services, but we only have Access 2000, which as far as I know is not capable of exploiting the sharepoint/xml back-end database features. Also, no one in the office here can share a directory on their workstation because they won't grant us administrator priveledges.
So thats how I came upon the idea of buying or creating cheap (<$250 USD) wireless network hard-drive on which to put the back-end. I'm mainly interested in knowing if it will work, and that the performance isn't going to be absolutely pathetic. I'm only looking at having 3 or 4 users at any one time, and the entire database will only house a couple thousand records.
We are creating a simple database to maintain driver license information for faculty, staff, and students who use cars from the university’s motor pool.
To do this, I have created two tables: tblDRIVER and tblLICENSE.
The fields in tblDRIVER are: pkfDriverIndex strLastName strFirstName strInitial strAddress1 strAddress2 strCity strState strZIP datBirthDate
The fields in tblLICENSE are: pkfUpdateIndex fkfDriverIndex datDateUpdated strState strLicNumber datExpirationDate ynViolations ynActive
Information about the driver is stored in tblDRIVER and the driver’s license information is stored in tblLICENSE. Periodically, we run a report that identifies drivers whose licenses are due to expire within a certain number of days. All this works fine.
My problem is that I am trying to create a lookup form that will load from a data entry form that will permit the Motor Pool Clerk to look up a driver by name and review the licensing information (which appears as a subform).
All this sort of works- I am using a combo box (based on a query) to look up a driver’s last name (which it does) and to populate all the driver’s information on the look-up form (including license information in a subform). Currently, the combo box locates the driver (including the unique index, last, and first names), and populates the form with first and last name but the rest of the information is not displayed on the look up form. Worse still, sometimes one driver’s last name matches up with the first name of the next driver listed in the table! This seems to happen only if a look up is attempted more than once. What gives.
My database is used by a few users on a shared drive in "read-only" mode so they can't change any data.I set a scheduled task to copy an updated version of the database (which I edit) every morning.
The problem is that when the users forget to close the database file I can't overwrite it.For this purpose I wrote a small code that quits the application at 00:00 using Application.Quit.The code WORKS when I test it on my computer, but every morning when I try to open the file I see that it is opened by another user since I also open it as "read-only" - meaning the code didn't work...getting the code to work properly OR get a better solution to be able to overwrite the file even though it's opened by other users.
Okay I know i've been incredibily stupid and made a tremendous mistake but what i need is the best solution to the problem i have right now... I have a database its msaccess with SQL Tables at the moment. There were an expected 40 wireless users expected but after horrendous crash on day one and only 10 users and after some digging i see that this is just not going to happen (why i assumed it would be ok is my own naivity and taking the word of the IT Manager)... the connection is totally unreliable and corrupts the database beyond repair.. infact i'd go so far as to say the wireless network murdered my database.. strong words but its my baby..
So what are my solutions here... the staff need this database... so what i have come up with are the following solutions and i thought i should ask for some advice before i plough ahead and make another fatal error..
use DAP? Or another internet based way of getting round it?
Get network points put in all the rooms?
Or can I make it totally SQLServer?
Help.. any advice would be greatly appreciated cause at the moment i have a fantastic application that just cant run and i feel such a complete failure.
For the past several years I have been designing and building Access databases. They are designed for small evironments to be used on one machine only. I am now faced with a situation where my client would like to have his database placed on his network server so it can be accessed by several computers. This is a little outside my area of expertise. I have searched the forum but I keep coming up with references to front end and back end and other things I don't understand. Can someone point me in the right direction to search for: what should be on the netword and what should be in the computer. what changes should I make to the database stand-alone vs. network. what unexpected problems should I expect.
Or perhaps you could suggest a book I could buy to assist me.
I have problem sharing an Access 2013 file from one cumputer and then change the data in the file on another computer, or i can change it but the change wont be made one both computers.
I'm working so i need my secretary to be able to change information or add, but i also need to get the change.
I have an access database that I created and setup user level security. I have encrypted the database and followed the directions of removing the admin from the admins group and created the new *.mdv file. When I access the database I get prompted for a username and password. When someone else from another computer accesses the same database they don't get prompted for anything and can go in and edit or access anything in there. Is there a way for me to secure the database up so they can't do this. The whole purpose of me setting up the User Level Security was for all users to have to login to there respective groups.
I'm doing some support for a company who's access is on a network. I think it must have been setup so that their login to the network determines whether they can access it or not, although it still asks for a username and password.
Anyway I have a local copy of the database and a username and password for the administrator. But I can't open the copy I'm getting the error
" you do not have the necessary permissions to use the "filename" object. Have your system administrator or the person who created this object establish the appropriate permissions for you"
I was hoping to be able to work on the database without having to be on site all the time. Is there anyway around this? or do I have to go back onsite to resolve it, and when there how do I do it :confused:
We have 11 computers on the network. One has an Access back end file. When we try to open this file via the network some of the computers can open it others get the follwing message.
"Microsoft Access cannot open this File
This file is located outside your intranet or on an untrusted site. Microsoft Access will not open the file due to potential security problems.
To open the file copy it to your machine or an accessible network location."
Do not understand why all the coputers cannot open the same access database file. Please Help Regards Keith
Might be a stupid question as I know a lot of access but it's the first time I'm doing this: What's the easiest way to deploy an access database (mdb) on a domain network to clients?
I was wondering if any of you have had experience firsthand or knew of reasons why an Access 97 database should not be installed on a WIndows 2000 network?
I am running a small access database over a wireless network which all worked fine (still does on 1 wired/3 wireless) with not too many problems total of 6 machines (5 wireless/1 wired). I have just replaced two machine as they were getting a bit old 3years. But these two new machines do not seem to have full rights to the access database, in that I can open the database and view records but when you add data you get a Disk Error message. I can open and share word documents etc but not the database – if I reverse this set-up I get the same problem the wired computer can open and save word documents but again not the database - what am I missing!!!
SET-UP = All machines have Windows XP Pro and Office 2003 with all windows/office updates done, all connected to the same workgroup etc. Two new machines are Dell with Dell Wireless adapter. No server just workgroup and database in a shared folder on one computer which is hard wired to the Netgear wireless router. I have not run any network wizards and I don’t think I need to, just sharing the folder should be enough? Windows is managing the dell wireless adapters, file and print sharing is enabled, other computers can print to this computer, but I just can’t get the database to share correctly – I have also checked “References” and all looks fine.
I have created the time booking application in access. (Application will alow autherised user to enter daily work done) My Idea was to put this file on the server and ask each employee to log in and enter information. But whenever I try to run application from other than my pc(On which file is created) it flashes error and can't run some of the form. It works absolutely fine when run from my pc. Why this hapens? What is the solution for this? Can access application is sharebale over network?
Ok.. I have done this before at another job, but this network (or stupid me) is giving me trouble. I'm trying to setup a database security (login/password) for a database on a network. I setup the security levels..setup a seperate workgroup... From my computer it logins fine with the correct workgroup.
Some of my users have laptops and usually at work finish, they remove their laptops. The issue occurs when they restart their laptops again without network access and then they have some dialog boxes showing below messages:
"Your network access was interrupted and you should close MS access and restart."
When OK is pressed, some other messages like " Object invalid or not set" appears and by pressing many time OK, it does not reset. Last option is to use "Ctrl+Alt+Del".
I have a small Access DB (multi-user) on a network that keeps turning into a read-only DB, with a message bar saying please save as . . . and it will not let you complete that. It seems to lock the application, and when I can get everyone out and copy the file out I can finally get it back to its normal state.
I have an ACCESS 2003 application with front end in the local machine and backend on the shared network drive. I mapped this drive to E: in my computer and all my linked tables show the E:folernameDatabasename.mdb as the source.
When I install this application in an other computer where they have mapped the same drive to F: , I am getting error that says "E:foldernameDatabasename.mdb" not found. How can use absolute network drive(like \cscrd eamfoldernamedatabasename.mdb) name to link the tables?
I want to link an excel sheet to my database but I dont want to link the location with a drive letter but instead linking the network address. How can this be achieved?
In addition, I want to startup application with a command line in a access macro and used this line but it doesnt work.
I want to link an excel sheet to my database but I dont want to link the location with a drive letter but instead linking the network address. How can this be achieved?
In addition, I want to startup application with a command line in a access macro and used this line but it doesnt work.
