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.
Guys, i need some hlp from u. i created a db and i was testing the security options. I remove all the ticks from the check box and now i can not do anything. i cant even use the right click.
how can i recover my access? any suggestion? thx max.
Code:Dim mysql1 Dim childid As String Dim Info As String Dim inputch as string dim inputin as string inputch = "Please enter the ID number of the young person" inputin = "If you have any comments about the young person" childid = InputBox(inputch, "Add young person", "") Info = InputBox(inputin, "Comments", "") Text16.SetFocus mysql1 = "Insert into [Activity ID] (ActivityID,ID,Information) Select [Forms]![Activityinfo]![Text16].Text, childid , Info" DoCmd.RunSQL mysql1
When I run it, It does the two input boxes fine, but it then asks you for the value of childid.. ?
Due to me still trying to grasp the basics of access, I have what I call the "Command Centre" which is basically a form where our administrators verify all records placed and control them from here.
As different stages of each record requires Authorising/Further Authorising by other users, they will require to update the same records as displayed on the admin control from.
The problem I have is that when the administrators make a change to a record which prompts an authoriser to go into the db and authorise, if the admin users keeps their form open (which is what I want), I understand that it doesn't save changes to the record until they exit the form. Naturally this causes problems for the authoriser.
Is there a way of saving changes to records as they are made so other users can edit the records as see it up to date. I'm thinking along the lines some vb code to save on an action.
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...
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.
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.
