if it's web enabled, it'd be a piece fo cake to make a mobile web page that allows you to do whatever functions you feel can be done by remote...

two issues here. first, you forgot to quote the url, so if you tested the vbs file from a command prompt to see if it works, you'd see it errors...

what happens to countries that have two part names, ie "United Kingdom", "United States", or "Federated States of Micronesia"?

woudn't you compact them and turn them to wrong values?

i though soundex didn't work if the value started with a number? so an address like 123 main street vs 321 main St was ineffective?

select soundex('123 main street') = 0000

select...

ok i just found an example on another forum that might help:

i've used a quick and dirty vb app that has a RichTextBox control on it. it has a single function; I pass it an ADODB.Field, which it places int eh...

sounds like yet another outsourcing to India to save money

i typically use a char(1) with a check constraint to allow only two values:

ie ALTER TABLE BLAH ADD GENDER CHAR(1) NULL CHECK (GENDER='M' OR GENDER='F')

I've seen this error in ADO when you stick a string into a varchar that is smaller than the string...ie sticka  30 character string into a varchar(20), and the ADO...

The magic tables are the virtual tables available in a trigger:

ie the [INSERTED] and [DELETED] tables, which can be referenced within a trigger so that you can add additional logic...

i would do this with three tables: as new/differet items are added, if they cannot use an existing attribute to describe them, it is added to the lookup table.

A similar...

could you have an uncommitted transaction that was created during testing, but never committed or rolled back?

in a nutshell, yes; you can change anything dynamically.

see sp_dboption in the BOL; also look in master and look at any of the stored frocs that start with sp_db or...

while the table definition doesn't allow variables, the DBCC command to change the starting value does:

declare @C1 int

set @c1=99

create table #sometable(id1 int IDENTITY(1, 1))

DBCC CHECKIDENT( [#sometable],RESEED,@c1)

this might help: i believe that error  Operating system error 21(The device is not ready.) encountered. means that the path to the device(in this case a log file) does not...