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.
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 seen some API that gets the serial of the hard drive, but this information is not unique and changes when the volume is formated. Does any one know of a way to return the orignal manufucture's information/serial which is unique(GUID) to the volume. Any Idea will be highly appreciated.
I've saved my Access files (as well as my Word files) to an external hard drive. I can open any Word doc from the hard drive, but when I try to open an Access file, it gives me the following error message: "can't find Language DLL msain.dll". What does that mean, and how can I fix it so that I can open an Access file from the hard drive?
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.
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.
Hello, I was needing some help coming up with the code to search the local hard drive and grab a file and then import it into an Access table. I'm trying to do this on a form if possible. If you know of another way, that would work. Any help would be appreciated. Thanks.
I have a db on a network drive and the performance is terrible, it runs fine on my local machine. How can I make it run better? The db is only 2 megs so I figured it would be ok, but since my forms have numerous queries within them, performance stinks.
I was just wondering how many users Access would be able to handle on a split frontend and backend database? The backend will be on a network drive and the frontend will be installed on each workstation. My database is pretty simple with no relationships if that matters. Also using Win7 and some users will have Office 2010 and others will have 2013.
I was using the database when there was a network error and I had to close it. When I tried to reopen it I got the error message: Record(s) cannot be read; no read permission on 'MSysAccessObjects'. I logged off the PC and logged back on various others, but keep getting the same message. Can anyone tell me if this is terminal or is there a way around it. I do have a backup, but it's a few days old and a lot of work will need re-entering' so any help would be appreciated!!
Alright, so my pride and joy and departmental savior database has been fully implemented and people are so pleased with it that they *all* want to use it at the same time. Initially, I made it custom for three peoples' UI preferences, but since it's such an intuitive design, other staff now feel comfortable using it instead of passing the work down the line to the one person who knows how to use that "newfangled thing".
A couple years ago, I used FMPro and allowing for multiple users at once was an annoyingly complicated process dealing with permissions and rights and accounts and passwords and yadda yadda. Is it any easier to set up in Access? Does anything special even need to be done to allow for multiple simultaneous users?
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 am attempting to link a table in one database to another database using the server name designation (ie.//2sxfprinff01Group) instead of the mapped network name (ie. G:). I tried relinking using the Access Link Manager. Right click on the linked table. But it does not let you edit the link.
Access 2007 does not allow this and reverts links to the G: drive. There are situations where the the IT department have set the mappings to this shared location as an H: for some of the employees. In those cases, the employee gets an error message telling them that Access cannot locate the G: drive.
An obvious solution is to get the employees remapped to the G: drive. However, one would think that MS would have allowed for mapping to the designated location and not an alias.
Here are some background . My company got a access file in a network drive.The data entry simply open the file in the network drive.But once the data has increased (~400mb) sudddendly,all process slow down. Like search , using report etc.Is there any method to imporive the situation?Some guys suggest me to copy the data file to the desktop and sync them.Can it it work?IF works,how to do that?
I have built a Database links to multiple back end databases. The whole database is completed, and I have to share it across the company, so I have placed the Database and all of the Back End databases on a "public" shared drive. I have the "public" drive stored as my Q drive. So when I link to the back end databases, the path it stores is Q:DatabasesDatabase.accdb
However, the problem is that not everyone will have the "public" drive mapped to Q. It's possible they could have it mapped to P or A or whatever. So if someone has their "public" drive mapped to P, this database will not work (since Q:DatabasesDatabase.accdb would not exist for them - it's really P:DatabasesDatabase.accdb).
Is there a way around this? So that instead of it mapping to the relative letter (Q or P), can it just refer to "public"?
I have a big (reasonably big) Access 2003 db which I have split. On the E: drive this functions perfectly. Years ago I moved it to an other drive and found that to reach the back end again I had to change the drive letter in the link to the tables. Unfortunately I can't remember how I did it - all I remember is that somehow I brought up the link path and could then simply change the drive letter. I now find it necessary to put the db on an external drive for use with different computers. It will probably be easiest to put "." instead of a drive letter in the link, but after trying all menu options for db, tables and macros I still haven't found out how to access the link path.
I've got a back end database on one of my computers and i'm trying to get the link tables to work over a network from another computer. Ive set the link tables up but it wont let me edit any data because it is read only. Its not read only when i run the front end from the computer that stores the back end. How do i enable the front end to edit the data over the network?
also, it is a multi-user system so i want multiple front end parts accessing the one back end but whenever i try and access the data from one system when another is already open it says the file is in use and i can't do anything!
I'm really stuck at the moment and i really need some help please! :confused:
My workaround was to temporarily map the URL to a vacant drive letter on the local machine, then copy the file over, then drop the mapped drive again. A bit clunky but doesn't incorporate much of a delay and this download only has to happen once per day.
The good news is, the file download / copy now works every time. The bad news is that removing the temporarily mapped drive after the copy has taken place, doesn't and I can't figure out why.
Here are the functions I use to map / unmap the drive :
Code:
Option Compare Database Option Explicit
Private Const RESOURCETYPE_ANY = &H0& Private Const CONNECT_UPDATE_PROFILE = &H1& Private Const RESOURCE_CONNECTED As Long = &H1&
[Code] .....
I have separate functions to check existing drive mappings on the local machine and thus determine an appropriate vacant letter to use for the temporary mapping - they work fine.
Unfortunately the UnMapDrive function returns False (even though I switch the active drive to C: and force the connection to be cancelled with the fForce flag) So the mapping always remains on the users profile.
I don't want to permanently map drives on the users' profiles, just briefly for the purposes of this daily file download.
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.
hi all, I'm just beginning to know the world of Access so maybe the solution for my problem is pretty simple. I have a huge database with Itemcodes, Costprice of materials and EffectiveDate (date on which new prices are valid). These dates represent past dates as well as future dates. The one that interests me the most is the most recent date in the past. What I would need is a query that filters out the most recent date per itemcode because right now there are several prices with several validity dates. Eventually it should result in a database that shows an item with one validitydate and one price. Right now the same itemcodes are repeated because different validitydates are related to it. I really hope somebody can help me out on this. Thanks in advance.
My DB has a table named noldba.int_member_history, which contains the following fields: member_id, date_start, date_end, member_status, iva_case_id, case_id,
It is possible for the member to have several lines of data under their same member_id like this:
20125626 12/1/1990 2/31/1990 N 21116625 20002717C 20125626 1/1/1991 4/30/1992 A 62574431A 20002717C 20125626 5/1/1992 8/31/2000 N 20006625 20002717C 20125626 9/1/2000 12/31/9999 M 21116625 20002717C 20125626 8/1/2000 12/31/9999 M 20111832 20090698C
So this member had 4 start and end dates under case 20002717C and only 1 start and end date under case 20090698C
I'm trying to write a query which is looking for member_id's along with a case_id which only has one member_status returned from the query and the member_status must be M. In this case the member has two cases which have the M member_status, but case 20002717C has other types of member status so I would not want the query to return the 20002717C case, only the 20090698C I'm sure Im asking for something that can't be done...but I'd never know unless I asked. Thanks
