HOW SHOULD I ADD MY STANDALONE DB TO OUR OFFICE NETWORK??? 1

[chubby]

program ACCESS 2000
OS windows 98 se
Network it's going to Windows NT 4.0
Total number of users 15

Purpose of the DB: Tracking personnel records. Entering new records, updating old ones, printing. Total number of records to date 11,000.

Problem-

1. Should I split the DB like it said to do in 'Access 2000 bible'? Or should I drop the whole DB in a folder on the share drive on the network and create shortcuts for everyone to access to DB?

Which with is better? easier for backups, upgrades

 

[svanels]

Not that I want to discourage you but check out:

http://databases.about.com/gi/dynam...tp://www.blueclaw-db.com/microsoft_access.htm

Don't forget the Table design link


From stand-alone to network? 98 to NT, before you start check out:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q300216

Be prepared to make some long days in testing



Steven van Els
SAvanEls@cq-link.sr

 

[chubby]

Thanks but I've ready tested it on the network for two week under heavy use. We've workout 95% of the bugs. I just wanted to know is it better to slit up my DB like it said in ACCESS 2000 BIBLE..

 

[Kjonnnn]

THE Access Bible says to split up table into tables of like information, then to relate the tables to each for effficiency.

Since we have no way of knowing how you've set up your tables and whether they are set up correctly, only you can truly answer that question.

 

[Kjonnnn]

THE Access Bible says to split up table into tables of like information, then to relate the tables to each for effficiency.

Since we have no way of knowing how you've set up your tables and whether they are set up correctly, only you can truly answer that question.

Your question is like asking... "Should I have my house rewired?" when you havent given us a clue as to how its wired in the first place.

 

[chubby]

Sorry, thanks for quick responses.
All 18 tables are linked by CASE #. The master table has the primary key which is the CASE # all the other tables contains CASE # field and thats how they linked.

Referential integrity is set, cascade update related field and cascade related records record.

need any more info?
thanks

 

[perrymans]

Do you mean split as in Front_End/ Back_End?

I prefer to use the split method, always, especially in a distributed environment. With a single databas eon a shared network, access will be slow as ALL data is transferred across, including forms and reports. With a split dBase, only the information is passed and the forms, macros, queries, reports, modules and so on are run from the users PC and won't eat up bandwidth and server processing power. Also, you can maintain a tighter control of you DB configuration by making the Front End a .mde and distributing that. It will prevent other people from changing the setup of your database or modifying your queries and forms and code.

SPLIT (if this was what you even meant in the first place)

Sean.

 

[chubby]

Yes, that's what I mean!!!! And about maintaining tight control of the DB configuration by making the Front End a mde and distributing that. Well, for this office preventing 15 women ages 37 to 64 from changing the setup or modifying anything is the last thing I have to worry about. One of my friends said I should convert tables to HTML for web or intranet publication.

I'm worried if an admin type, a case workers or zone supervisor wants a report built or a form add-on for everyone use? With Front_End/Back_End idea I'll have to update every computer when changes are made to forms, reports, macros, etc? Is this the way to go or not???

 

[perrymans]

Definitely. Those ladies may not be programmers, but that deosn't mean they aren't going to go poking around and may delete something. No matter what, for multiple user's, the front end should be on the PC to conserve time. No one will want to use a "new" system if they have to wait for a form to load and the query to run. Save your server powere for good. Otherwise bothe the server and the PC have to do the processing, instead of just the PC.

With that said, if you are going to put a front end on a PC, make it an mde. It is easy enough to update. My feller's have the file sharing turned on to their desktops and if I have a new release, I just drop it onto their desktop and overwrite the existing mde. You'll find many good tips on this site and the FAQ about distributed updating, but it was more advanced than what I needed.

Theoretically, there won't be many changes after you get everything working, and if you drop them on the PC for them from Windows Explorer, they won't even realize they just got an update.

Also make sure you disable the database window under Tools>Startup. I'll get blasted for this I'm sure, but it will keep the ladies from trying to take shortcuts past the forms and entering the data directly into the tables. I say I'll get blasted because it is easy to get around this, but as you said, you're not keeping out programmers, but women who don't care enough to break into it.

Sean.

 

[chubby]

Hey sean, you should be a darn teacher. You just made me a totally believer. "Thanks for the tips, I'll DO IT!!

I'm not a VBA or SQL programmer, but placing 10 different excel files in Access help solve a lot of problems. Now everyone can use and see the same data, call up reports and they even have 13 charts that are automatically produced.

I love this site!! With people you like you who's needs a book. thanks again....
Chubby