• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

ACCESS 2000 (YES I KNOW IT SUCKS)

FettsBabe

Diamond Member
I need to create a database (Access). I work in a legal field and I want to push information into the database from an excel spreadsheet, then I want to click on certain cases and produce mass quantities of judicial forms. Such as, if I need to seek judgments on 10 people, then I select those 10 people and it pushes their personal information into the form and I can print it out.

The county has to go on the form too, and NC has alot of counties, so I need to create a list of counties with their addresses, and I need it to pull the respective address and put it in the document.
 
You can inport an Excel Spreadsheet easily into Access - there is an Access wizard to help you do that.

How you select and manipulate the info them becomes a design decision.

You will need to lay out the actual steps on paper and then determine the equivalent daabase type commands.
 
Bring that down to big bird level please!!!!

Seriously, I know how to inport the excel spreadsheet. Where do I select and manipulate the documents? Where do I get the database commands. Give me an example...my degree is legal, business, accounting and tax. i'm lost at programming/commands.
 
1) You will need a table in the DB that has the list of counties along with specific info related to the county (POC, address, etc).

2) Within the DB, there is no such thing as a document. You have tables contain fields of data.

You can develop queries (simple questions) to extract data that meets certain criteria that is built into the query.

You can have entry forms that allow you to select data choices.
Those choices can be hard coded into the display form or pulled from the database.

You can generate reports from the database or fire off an application that can support files of certain formats (PDF as an example).

Stop by a computer store and pick up Access For Dummies to get you started.

What you want can be done by a noob; however, you will have to have some patience and a lot of trial and error in getting things to work the way you desire.

The first is to document step-by-step exactly how you would handle each task if you had a spreadsheet and a filing cabinet of information.

If you were to have a form that displayed all cases; you could select the case and have a query extract all information that is keyed to that case.

The critical area is how you tie the information together so it can easily be retrieved into the forms and followup manipulation
 
Access 2000 is just fine. It has almost all the features of any later version, upgrading is almost pointless from 2000 to anything else. The big improvements past 2000 are mostly around reporting. Now, if you had '97 that would suck, but could also be worked around.

Anyway, what EagleKeeper is saying is getting data into access is only the starting point. It sounds like you are entirely new to Access, or any database at all really. Access does not require programming language at all unless you start wanting to do some of the more interesting things. This is as basic as I can make it wouthout having to type a access book, which you can get at a bookstore, or by reading the help built into access. These comments below are based upon your really short description, and could be more or less required.

First, get the data into access. You will need client data. I see tables as:
name, address, contact info (can concievably be all one table). there needs to be some kind of ID in this table, either an autonumber or the clien'ts name thatw ill be unique so you can find it later
state and county table for lookup. Can be a match between county and zip code using TIGER line data from the government which would allow linking a client's zip to the correct county. (fields: state, zip code, county FIPS code, county name)
a table for each legal form. Include the client's ID from above.

Once the data nad tables are set up, you need to create a form for each table. These are the ones I see:
client lookup (find aclient, and all related forms.)
add client (form to add a new record to the client table)
one form for each legal form table created above. This should require client ID, or be a linked subform sot hat the form is attached to a client.

From there you have a few options for how to get data out of the database. You can either:
Integrate with Word so that the data is puleld from the database into a word document for printing. (hardest, but looks the best and most professional. Requires programming using VBA to do it correctly)
design a report to print the forms for a client (middle difficulty, looks slightly better than printing the form itself)
print the access form itself (easy, don't look good)

Originally posted by: EagleKeeper
Stop by a computer store and pick up Access For Dummies to get you started.

What you want can be done by a noob; however, you will have to have some patience and a lot of trial and error in getting things to work the way you desire.

The first is to document step-by-step exactly how you would handle each task if you had a spreadsheet and a filing cabinet of information.
Listen to EagleKeeper. figuring out requirements should be 3/4 the time, designing it should be 1/4 or less. If you don't spend the time doing the requirements you will end up having to redo large portions of the database or, in the worst case, have to start over.


 
Originally posted by: FettsBabe
how much time will it take to get to the finished product?

For you? My estimate would be 2-4 hundred hours. Rough estimate based on what you have spelled out and the skill level I think you are at.

For you working with someone who knows Access well? probably 60-100 for you 20-40 for the programmer and 10 or so working together on requirements, depending on just how far you want to take this. Less requirements, or spelling them out very specifically will take less time in the long run. If the access person has done something before that is along the same liens it can likely be leveraged to reduce that time dramatically. So 90-150 hours total.

EagleKeeper is exactly right, this can be done by a n00b. But the less you know the longer it will take. You are better off spending the time at the front then trying to add stuff on later, which is what you will do if you don't spend the time now, I guarantee it.
 
Getting the data into access is the easy part. Designing the forms/reports is the hard part. It sounds like the reports would need to have the look of legal forms that already exist. I agree with Evadman, this could easily be a week long project for a full time developer, maybe even longer depending on the number of forms needed.

 
Back
Top