Database Design / Access

[The Warrior Monk]

Anyone familiar with designing databases in MS access?

The maximum number of properties will be less than 100,000.

I need to store picture files, the number of which will vary for each property. I also need to store other documentation for the property, such as surveys, copies of listing sheets, etc., the number of which will also vary for each property.

Would you

1. Store the various types of files one large folder (i.e., one folder for db);
2. Store the files related to each property in a folder for that specific property (i.e., 100,000 folders).

Any suggestions appreciated.

 

[Randy Pippin]

I'm not quite sure what you are doing but since I've gone paperless I have;
1. Created a Folder labeled 2008 on my desktop
2. When that folder is opened I have created a folder for each month.
3. After opening the folder for any month I will see separate folders for each appraisal I did that month.
4. Upon opening any "appraisal folder" I see all information about the subject. A copy of the order, legal description, plat, Flood map etc.
5. I also see 2 other folders, 1 labeled comparables that contains a copy of the MLS page of every comparable I considered and another folder labeled "pictures" which contains a copy of every picture I took of the subject and all comparables on that one appraisal.

It's not as sophisticated as it could be but it is easy to maneuver around in and find any information I look for.

 

[The Warrior Monk]

I plan on either merging or connecting the all of the databases we have (assessor, appraiser, and listing). Miscellaneous documentation needs to be referenced which is not included in the existing database. Photos (jpg), nonoffice listing sheets (pdf), and other documentation (probably bmp) will need to be linked.

 

[Howard Klahr]

David,

Here is a link to a CRM program designed for commercial real estate agents. You can download a demo version. This program has the ability to incorporate photos, images, files, etc to the contact records. I believe this program was built on a MS Access platform. You might get some good ideas on database design, layout, structure. Hope this is helpful.


Realhound

 

[Tony V]

Dave....my thought on this type of project would be to create a folder for the entire project , a subfolder for District, then in each district folder a sub folder for sections 1 thru 10 then a folder for each block finally a file for each lot. It would be the easiest way to find a property..

 

[Tejus]

1. Identify the user requirements.

2. Design a system which meets those requirements.

3. Implement the design, taking into account implementation trade-offs.

4. Use a small but diverse data set to test your implementation.

4. During the above steps, when you identify issues in your requirements/design/implementation/test, backup to an earlier step, address the issues and continue forward.

5. When completed, step back and review the end product. There is a high probability your 1st requirements/design/implementation/test attempt will have numerous shortcomings due to lack of understanding of the problem. If necessary, start over on Step 1 with your better understanding of the problem and redo the process (most sw companies make a living doing this, it is called upgrades).

6. Repeat til the users are happy campers.

buene suerte.

 

[deturner]

David,

I have built numerous Access DB's and once worked for IBM as the Access specialist. I'd be happy to communicate privately with you and see if I can help

DaveT in NC

 

[jdbiggers]

I'm not sure I would use Access for the project for that quantity of data unless you have lots of free time on your hands and have a passion repairing and compacting tables. If you don't know what that is, hat is an indication you shouldn't use Access. There are some "ready-built" databases you can use available on the internet, kind of mini-MLS systems, some of which are free. You might want to look there.

JD