I transfer my Access DB to SQL Server 2000

the best way is to use Access 2002 (XP) upsizing wizard .... it trasfer data , RELATIONSHIPS, INDEXES, defaults and many other...

also you must take care that CREATE DEFAULT is usefull if you want to change the default for all columns from 1 place (from 0 to null as an example)...

of course to install MDAC and its SP to connect correctly to SQL Server..

also there is a topic in SQL BOL that is "Resetting the Suspect Status" that tells you...

what about:

1- installing SP1 on win XP clients

2- and installing SQL Server sp3a on server

3- install MDAC 2.7 RTM refresh on Server and clients machine ... and see...

I think the best thing is to write 1 Stored procedure (not to write the trigeer on it .. or on the table ..)

and this can be reashed by checking...

of course apply SP3a .. it solve a lot of several pugs in SQL Server 2000

did you make a scheduled maintainance plan to rearange your indeses and upade statistics...

of course the "timeout expired" is a deadlock message .. because one had gone into Lock waiting until its lock_timeout is finished.

but the problem you may face is...

you can write 2 stored procedure (1 for de attach and 1 for attach)

and make a Visual Basic Program that :

1- call deattach stored procedure

2- copy the file ......

if yuo are selecting data then the best way is to call a View ... or join 2 or more views together .. and in Views write "with (nolock)" in...

you can make a VB program that read from the registery and then use this in SQL

xp_cmdshell "c:\myVbProgram.exe"

does there anyone using these tables (select , update, ....) when you insert your data ... if yes .. then you have a locking problem from the users that uses...

if every thing in your calculation is okay .. and you are sure that there is no Overflow/Divide-by-zero error ... then restart your server ... the same error happened to...

use this in the query analyzer

ALTER DATABASE database SET MULTI_USER

This command returns access to the database to its normal operating state.

yes if you want the DB to keep running .. then the best solution is to make FGull backup in this moment .. then create the same DAtabase NAme on...

you have to (set lock_timeout) in SQL server query analyzer .. which sets the maximum amount of time that SQL Server allows a transaction to wait for the release of...