I’m using PHP to get each record. There isn’t much on the web about working with timestamp fields in PHP, so I created the function below to convert and store the OLToken as an integer:

function ConvertOLToken ($theToken)
{
   $OLToken = "";
   for ($i = 0; $i < strlen ($theToken); $i++)
   {
      $Byte = dechex (ord ($theToken[$i]));
      $OLToken .= str_pad ($Byte, 2, "0", STR_PAD_LEFT);
   }
   return hexdec($OLToken);
}

This value is passed back to stored procedures as an integer parameter and used in stored procedures:

IF EXISTS (
   SELECT 1
   FROM [Table]
   WHERE [ID] = @pID
      AND [OLToken] = CONVERT([binary](8), @pOLToken))
BEGIN
...
END

SELECT [ROUTINE_NAME], [ROUTINE_DEFINITION]
FROM [INFORMATION_SCHEMA].[ROUTINES]
WHERE [ROUTINE_DEFINITION] LIKE '%<insert_text_here>%'
AND [ROUTINE_TYPE] = 'PROCEDURE'

[Via: ASP FAQ]

It uses concurrent AJAX, calling a lightweight PHP+XML web service layer to communicate with a Microsoft SQL Server.

The management application that the staff at the Links use to administer the bookings is written in C#, using C# web services back to the SQL Server.

Like the online booking, the AJAX layer is based on "The Ultimate AJAX object" by Patrick Hunlock, which I’ve found to be one of the only objects that elegantly supports concurrency.

It uses concurrent AJAX, calling a lightweight PHP+XML web service layer to communicate with a Microsoft SQL Server.

The management application that the staff at the Links use to administer the bookings is written in C#, using C# web services back to the SQL Server.

The AJAX layer is based on "The Ultimate AJAX object" by Patrick Hunlock, which I’ve found to be one of the only objects that elegantly supports concurrency.