 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / Multiuser / Networking / April 2005MS Access network ver.
Hello, can somebody please explain to me what ms access version should i use for mutliple users? is there an ms access network ver.? i will appreciate your help. thanks! vy Read your post from yesterday. > Hello, > [quoted text clipped - 4 lines] > > vy hi rick! i ddin't get any response from my yesterday's posting. i saw your response to a posting similar to mine, can you give me some thoughts about mine. i don't know if there's such a thing as ms access network ver. or what we can use for multiple users? thanks! > Read your post from yesterday. > [quoted text clipped - 6 lines] > > > > vy Your post from yesterday has SEVERAL responses. go look at it. > hi rick! > [quoted text clipped - 15 lines] > > > > > > vy Make that "2" posts. One from me, and one from an MVP. Rick B > hi rick! > [quoted text clipped - 15 lines] > > > > > > vy i can't find it. there's just one post dated 03-31-05; running slow report..., i can't find mine. > Make that "2" posts. One from me, and one from an MVP. > [quoted text clipped - 22 lines] > > > > > > > > vy From John... >help! i'm developing a database, very complicated one and it will be saved >in a server. there will be multiple users for this database, what version of >ms access can i use? 1.0, 1.1, 2.0, 95, 97, 2000, 2002, or 2003 should work just fine. Access is multiuser out of the box. >is there such thing as ms access network version? All of the above. What you'll need to do is use the Database Splitter Wizard, or manually split the database into a "Frontend" containing the forms, reports, queries and so on, linked to a shared "Backend" containing only the data tables. Each user will need Access installed (either retail Access or the "runtime" available from the Developer's Toolkit), and a copy of the frontend. John W. Vinson[MVP] > i can't find it. there's just one post dated 03-31-05; running slow > report..., i can't find mine. [quoted text clipped - 25 lines] > > > > > > > > > > vy From me... Any version of Access will work. Each user will need Access on their local machine, unless you plan to purchase the developer's edition and package the database application with a run-time version of Access. Do your users all have the application? How many users will you have? Are you a pretty advanced application developer? Rick B "sparkle_vy" <sparkle_vy@discussions.microsoft.com> wrote in message news:AD26B899-5E84-45B8-B1C1-87150EBF1C46@microsoft.com... > help! i'm developing a database, very complicated one and it will be saved > in a server. there will be multiple users for this database, what version of > ms access can i use? is there such thing as ms access network version? > i can't find it. there's just one post dated 03-31-05; running slow > report..., i can't find mine. [quoted text clipped - 25 lines] > > > > > > > > > > vy thanks! i got the one you forwarded from mvp too. there will be at least 10 users who will update and work on the database. i was wondering why is it that when my coworker tried to open the database while i am also using it didn't allow her to open the database. and we're using ms access 2000. it's not allowing us to open/update at the same time. yeah, the users have the application on their own hard drive and the database file is saved on the server. nope, im just learning to use ms access, i know a little of c++ and that's it. i will need alot of tips to finish a project. thanks > From me... > [quoted text clipped - 52 lines] > > > > > > > > > > > > vy Do you all have FULL access to the folder in which the database lives? When one person opens a database it creates a lock file (ldb) in the folder. When the next user opens the databse they update that file. When the last person using the database shuts it down, they delete that lock file. Full windows permissions to the folder are needed to perform those tasks. Rick B > thanks! i got the one you forwarded from mvp too. > [quoted text clipped - 66 lines] > > > > > > > > > > > > > > vy every body have full access to the folder where the database is saved. how do i do that, to activate/deactivate the full windows permission? > Do you all have FULL access to the folder in which the database lives? When > one person opens a database it creates a lock file (ldb) in the folder. [quoted text clipped - 86 lines] > > > > > > > > > > > > > > > > vy Your system administrator who creates the network logons should be able to set the appropriate permissions, or tell you how. Rick B > every body have full access to the folder where the database is saved. how > do i do that, to activate/deactivate the full windows permission? [quoted text clipped - 89 lines] > > > > > > > > > > > > > > > > > > vy i see, so access 2000 can be used and updated by multiple user, only if the administrator changes the network logons that will allow everybody to use the database. thanks rick! > Your system administrator who creates the network logons should be able to > set the appropriate permissions, or tell you how. [quoted text clipped - 112 lines] > > > > > > > > > > > > > > > > > > > > vy > i see, so access 2000 can be used and > updated by multiple user, only if the > administrator changes the network logons > that will allow everybody to use the > database. thanks rick! To add to Rick's very good advice, just a word of caution -- if you are doing anything with Access 2000, make certain that you have all three Service Packs applied, and all other updates. Even so, I'd feel more comfortable with Access 2002 or 2003 with all Service Packs and updates. And, covering other general topics on multiuser, there's an introductory presentation on Access in a Multiuser Environment that I did for my user group that you can download from http://appdevissues.tripod.com. It will identify topics that I thought worthwhile to discuss, and a bit more. The best collection of detailed information and links on the subject of Access in the multiuser environment is at MVP Tony Toews' site, http://www.granite.ab.ca/accsmstr.htm. Larry Linson Microsoft Access MVP i only saw 2 postings for 03-31-05: compacting and reparing and record locking, i can't find mine. > Make that "2" posts. One from me, and one from an MVP. > [quoted text clipped - 22 lines] > > > > > > > > vy You did not post it in the multiuser newsgroup. you posted it in microsoft.public.access Rick B > i only saw 2 postings for 03-31-05: compacting and reparing and record > locking, i can't find mine. [quoted text clipped - 25 lines] > > > > > > > > > > vy i don't even know how i did that. it was my first time to do this yesterday. thanks for letting me know. > You did not post it in the multiuser newsgroup. > [quoted text clipped - 34 lines] > > > > > > > > > > > > vy Sparkle, I think Rick B spent more time referring you to a previous post than it would to have answered the question. Any verison will do; however, I would recommed at least 2000. Now, there are some issues regarding multi-users. Get a good book on Access that will explain it in detail. The short of it is: Once you have your application to a point where the tables and indexes are defined, use the database splitter to create a back end database. It should contain data and only data. All other object should be in the front end. Put the back end mdb file on a server where all users have rights. Distribute the front end to the users for them to put on their own PC. Be sure to use absolute addressing in you table links since all users will not have the same drive mappings. Be sure you address record locking. The more users you have, the more important this becomes. It is too involved to discuss here. Read you book. Good Luck > Hello, > [quoted text clipped - 4 lines] > > vy |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.