Steve, >It will use a database, so your solution is viable - only difference is that we will need hundreds (possibly thousands) of clients to supply phone number and service provider. It may take a while, but there's no reason why it can't be done.
Another coincidental benefit to using the e-mail gateways is that it obviously also works to send an e-mail as well. So, you could make your field generic, like "EMailNotifyAddr". If the person wants an e-mail, you put in their e-mail address, if they want a text message, you put in their cell phone text message address. By the way, even if you were using SMS Messaging directly, I am sure you have to identify the recipient, I assume by their cell phone number. The only additional info you need with this method is the carrier. The web page link I sent you has nearly all the carriers and if it is not found there, I imagine you could go to the carrier's web site and get the gateway information. I have had to deal with getting the carrier for projects in the past. It was easier then because you could assume that a given areacode and 3-digit prefix would always be the same carrier. So, once you knew who the carrier was for one, you could assume that all the others were the same carrier. I am guessing that would still hold true for the vast majority of numbers, but since the number portability legislation was passed, people can change to a different carrier and keep their number, so you can't be sure. If I had thousands to do, I would start by getting a unique list of areacode and 3-digit prefix combinations, find out who the carrier is for one of them and assume all the others are the same carrier. You could then manage by exception by sending an e-mail to everyone letting them know you are going to send a test text message. Then send the test text message and followup with another e-mail asking for a confirmation from everyone about whether they received the text message or not. Glenn Lawler www.incodesystems.com -----Original Message----- From: Wilson, Stephen [SMTP:[EMAIL PROTECTED] Sent: Tuesday, October 16, 2007 4:46 AM To: [email protected] Subject: RE: [delphi-en] re: sms messaging app using delphi 5 Glenn >> If your app is not using a database It will use a database, so your solution is viable - only difference is that we will need hundreds (possibly thousands) of clients to supply phone number and service provider. It may take a while, but there's no reason why it can't be done. Thanks to all again for your help. Regards Steve *************************************************************************** This e-mail and any files transmitted with it are confidential. If you are not the intended recipient, any reading, printing, storage, disclosure, copying or any other action taken in respect of this e-mail is prohibited and may be unlawful. If you are not the intended recipient, please notify the sender immediately by using the reply function and then permanently delete what you have received. Content of emails received by this Trust will be subject to disclosure under the Freedom of Information Act 2000, subject to the specified exemptions, including the Data Protection Act 1998 and Caldicott Guardian principles. This footnote also confirms that this email message has been swept by MIMESweeper and Sophos Anti-virus for the presence of computer viruses. *************************************************************************** ----------------------------------------------------- Home page: http://groups.yahoo.com/group/delphi-en/ To unsubscribe: [EMAIL PROTECTED] Yahoo! Groups Links
