shovels

You could do something like this... You may need to add some validation, but the best part is that if you create more username/password fields in the form you won't have to change the code - it will just loop through them all [code=php] // Initialise the array - beware …

If you want to do it your self, as far as I know, you will need an audit (anyone who comes into contact with card numbers) These, I believe, are quarterly and cost a substantial amount. Unless you are going to be processing 1000's of transactions you are better of …

Are buyers going to be 'searching' for properties by entering criteria? Then you want to return the properties for sale that match that criteria?

Do people have to be registered to access the files? If you can get the people to register first you could prevent non-registered members from accessing the files at all. Another option could be to serve the files using PHP, possibly not the best way of dealing with the files, …

For 300 recipients you could write a PHP script that loops through an exported CSV list. Use the PHP mail function to send a customised email to each recipient individually. The main problem will be that if you do too many emails in one go you may run into problems. …

Why not just add a timestamp to the SQL statement? I would also try to avoid using such names as time, date, etc for field names in a databases as this can cause problems. For example: $sql="INSERT INTO $tbl_name(username, password, level, email,fname,lname,time)VALUES('$uname', '$pword', '$level','$email','$fname','$lname', Now())";

I had a similar issue with a site I wrote recently, and if I'm understanding your question you should be able to append QSA to the end. For example: ReWriteRule ^sub_folder/page.htm$ actual_page.php [L,QSA] Any parameters added onto the end of the url will be delt with in the 'normal' way.