Showing posts with label phone. Show all posts
Showing posts with label phone. Show all posts

Monday, March 26, 2012

mobile phone and databases

Can you please tell me what are the risks of customers using a mobile phone to send a request of information which will be automatically responded to as an entry is made into the database.

How do I ensure that the data intergrity is maintained, as this 'Table' in the database will take in many request a day and repond based on what the customer has type in on the text message.

I did not get your point. What are you trying to do ? Sending a message to a Service, processing it in the database and sending the processed data, evtl. with a customized text back to the caller ? Data integrity should be maintained either through constraint rules (Whatever rules you have) or your logic you are trying to implement in the midtier or the database level.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Friday, March 9, 2012

Missing SET keyword.

Using the following update command I get the following message

UPDATE Last, First, [Card Number], [Phone Number], IDKey
FROM dbo.LibUserS

error:

Missing SET keyword.
Unable to parse query text.

incorrect syntax near ','

thats correct. The update statement requires the fields to update as well as on which record you want to update. Example:

UPDATE [TableName]

SET [FieldName] = someNewValue

WHERE [fieldName] = SomeValue

typically:

UPDATE [dbo.LibUserS]

SET Last = @.p1,

SET First = @.p2,

SET [Card Number] = @.p3,

SET [Phone Number] = @.p4

WHERE IDKey = @.IDValue

the @.parameter is the parameter you supply in the query on the command object (OleDbCommand or SqlCommand, whichever database connection/driver you are using) so it can take those values and replace them with the @.parameter "placeholder" if you like.

|||Helped, perfect, Thanks!