Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 Import/Export (DTS) and Replication (2000)
 Upsizing Access to SQLServer "invalid use of null"

Author  Topic 

PaulXLE
Starting Member

3 Posts

Posted - 2008-12-16 : 12:56:54
I'm trying to upsize an Access database to SQL Server 2000

I'm using Access 2007, and the SQLServer database is on-line (hosted by Fasthosts) and it's version 2000

Following Fasthosts instructions I get to the point where I've specified the target database using the Wizard, selecting a "machine data source" entry I've made, which I know works okay (Access can see the data on the SQLServer using it)

Having entered the password to "SQL Server Login" I immediately get a dialog box "Upsizing Wizard" and an error "Invalid use of Null".

If I get the password wrong, I get a suitable error - not the above, so it does appear to be getting somewhere... and it doesn't matter which Access database I try and upsize, including a totally empty one.

I have seen mention of this error elsewhere on t'internet, but never with an explanation.

I'd be very grateful if anyone could help! TIA

Paul

PaulXLE
Starting Member

3 Posts

Posted - 2008-12-19 : 14:00:33
Okay, replying to self... nobody knows about the Null thing... fair enough

So, I did this... I upsized my Access database to my local machine, running SQL Server Express, which worked fine.

I then scripted the entire database, and then ran this script on the remote SQL Server, and lo, my database is upsized!

My question is... ah but is it?

I'm no expert (yeah, you could tell) but is this a valid way to do the job, or does stuff get lost when you do that scripting thing?
So far the data looks good.

Paul
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2008-12-19 : 14:07:29
I wouldn't recommend that scripting thing as it could miss some stuff. After you've upsized to your local machine, either do a BACKUP/RESTORE or detach/attach to get it to the remote server. Both of these methods ensure that you grab everything from the user database.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

PaulXLE
Starting Member

3 Posts

Posted - 2008-12-23 : 10:49:36
Thanks for that advice

However... as the SQL Server in question is hosted elsewhere, I don't think I can run a Restore on it, at least I don't see how to.

In the hosting company's instructions for restoring a database they actually recommend the scripting method to restore a database.

my database is quite simple, lots of tables but no great complexity, no queries to carry over, just data really.

you said I might lose some stuff... what sort of stuff should I be worried about, presumably not actual data?

TIA

Paul
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2008-12-23 : 11:05:41
Make sure all of your constraints, indexes, and any other objects get copied over.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page
   

- Advertisement -