??

the parens around the 1.0 are superfluous.  actually many of the parens are.  this is equivalent:

isnull

([UnitPrice] * (1.0

wait a sec, did I understand this right?  you are changing the datatype of a table column from within a proc? 

if so then you should rethink your design.  the schema...

the example shown has you backing up directly to a network share.  generally that's a bad idea because if the network goes down, your backup fails.  backup failing is bad...

this may help you out:

http://www.microsoft.com/sql/solutions/migration/access/default.mspx

Generally you do not want to have the data/log files on the C: drive.  that's the OS partition, so if your database gets large and the C: drive fills up,...

why on earth would you want to name your objects like that?  that's very non-standard.

mixing different types in the same table is really just the EAV model, which makes me ill.

Here's an amusing commentary on the EAV which I agree with:

http://weblogs.sqlteam.com/davidm/articles/12117.aspx

you might benefit from reading this:

http://www.datamodel.org/NormalizationRules.html

ESRI has the ArcSDE extensions for SQL Server as well, not sure if you've looked at that at all.  I know of it, but not more than that I'm afraid,...

this might be of use:

http://www.microsoft.com/sql/solutions/migration/access/default.mspx

why not just use bcp.exe?

this works too, if a bit weird looking:

declare @cr varchar(2)

set @cr = '

'

have a look at sp_spaceused. you could run it in each database to generate a report.

you are doing some weird stuff there.  you would probably be better off putting this logic in sprocs rather than VB. 

anyway, on to your question: have a look at the...

ok. 

I was just making sure that people don't read the thread and leave with the impression that string formatting will protect you from sql injection. 

because it won't.