been in the business too long..
This is an automated response....
Specification - first draft
Expat Database for the Dominican Republic
Description
A searchable database with web-based data entry forms containing personal, geographic, hobbies and interests, skills and health information about expats in the DR.
Preferred development environment
PHP/MySQL
Functionality and Use
Robert, you can fill out the remainder!
Access Restrictions and Databse Ownership and Availability
This is the one issue that bothers me about this type of thing - I do not particularly want for example my ex-husband's new wife searching out exactly how old I am
Example, I found out a few months ago that said ex-husband donated 1,000 South African bucks for the development of an Indie film - I could have stayed without this information as it just pissed me off - given that the bum never paid any child support.
And this all on the internet....
Another issue that bothers me - the business of providing addresses for spammers. This database sounds a perfect harvesting ground for this --- (I have had to delist myself on a few databases for South African expats for exactly this reason)
The internet is a wonderful place and I work in cyberspace daily. But, for having my information floating about even for the best of reasons, does not seem a good idea to me. So, my vote would be NO! for a public searchable database. For a non-public, request based database, where a request goes to the database, the 'receiver' is contacted to verify that he/she wants to divulge the information, and then only information is released, my vote would be YES.
So the question is, how far do you want to go (read how much do you want to spend) for a database development such as this Robert? And, can your current profile functionality on DR1 not be simply extended a little to cater for more geographic, interests and hobby type information? Seems to me that you have the basics in place with the profiles and the private messaging?