Gary Stainburn wrote: > Hi folks, > > I'm after general ideas and pointers for a project I'm likely to get > lumbered with. > > At the moment we have a membership database written in access on a > windows box. One person is responsible for keeping this up to date > and then distributing the updated file for others to use - e.g. for > mailshots. > > Now, with growing membership numbers, two people in seperate > locations need to update the file, and more people are needing read > access to it. > > Ideally, I would like to put some sort of web front end on it, hosted > on one of my existing web servers - running standard RH7.3+errata. > > I'm not bothered how the data is stored on my server (my database of > choice is PostgreSQL anyway)
Excellent choice! > as I'm only going to be doing simple > insert/updates and selects. > > The main thing I want to be able to do - if possible - is still allow > the file to be available as the existing .mdb so people can continue > to use it with existing MS Office mailing list type documents. 1. There is an ODBC driver for PostgreSQL available, so the MS products could use an ODBC data source for the mailing list. 2. You can easily export the PostgreSQL data to a variety of formats, from simple text-delimited to Excel worksheets (using Spreadsheet::WriteExcel) that could be mailing list data sources. 3. You could write some code in the Access database to populate its table from the PostgreSQL database using ODBC. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
