I think your choices are either

a) Move the files to a UNC location accessible by both you/your machine and the server e.g. \\myserver\myfolder

or

b) Use the VB app to connect...

Currently, the version of SQL Server that comes with SBS 2003 Premium is 2000 so, yes, it is the same. It is used initially to manage the Sharepoint implementation...

No problem. HTH.

Okay, I understand, but trying to flatten it into one table is actually more difficult that splitting it out. Keeping it in one table only makes the sql:relationship annotations...

The first thing I would look at is your table schema against the xml schema. Do you need two or three tables e.g. Buyer, CoverageEntry & ZipCode or are...

me too

Your question is too vague. What do you want to know ?

I've just answered your other post at http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=21&messageid=260920 regarding xpath and that, like this, look more...

preceding-sibling::node()[text()=following-sibling::node()/text()][1]

That won't work when a persons birthday has not yet occurred in the current year e.g. someone born on 1st April 1973 would be 33 according to your function now...

It's not pretty but here's a stored proc that executes a specified statement and returns the resulting FOR XML as a proper recordset which can then be inserted, queried etc....

XmlSpy can create a xsd schema from a database structure and can also export database data to xml. I use XmlSpy quite a bit though and I don't know...

When execting the bulk load have you got the KeepIdentity property set to False ?

Two things really, firstly are you sure your SQL Server name is localhost in the connection string ? Should it be (local) instead. Secondly check your windows account's...

the xml is invalid i.e. the Features element is not closed.

You can use various tools to generate schemas from sample data files (e.g. XMLSpy) but you would still have to add the sql mapping stuff yourself. The generated schemas...