Importing MS ACCESS db into MS Sql Server 2000

I have a ms access database on say c:\database.mdb
I have a sql server 2000 running too.
I want to use some command line tool , like isql or osql to convert this database into a sql sever database.
How can I achieve this ?
Thanks in advance.
Alok.You can use SQL server's DTS tool to import MS access database to SQL server.
If not you can use MS Access Upsizing wizard to upgrade to SQL server.|||As I mentioned , I need to do it through command line.
If you give me a sample code , that would be great.|||After creating the DTS package run DTSRUN utility from command prompt to execute the package. Refer to SQL server books online for DTS topics and DTSRUN topic for more information.

Importing data from oracle to sql loosing data after the decimal point

I have created a simple package that uses a sql command to pull data from an oracle database and inserts the data into a sql 2005 table. Some of the data fields that i am pulling from contain two digits after the decimal point, however this data is lost when it gets into sql. I have even tried putting the data into a flat file, and still the data is lost.

In the package I have a ole db source connection which is the oracle database and when i do the preview i see all the data I need. I am very confused and tried a number of things to get the data into sql, but none work. Any ideas would be very helpful.

thanks

What is the data type of the SSIS column that you are storing the Oracle results in? Also double check that you have a "scale" defined for that data type.|||

I have tried money, decimal (38,2) , float and numeric (18,2)

With no luck. What is really weird is that when I use the Destination of flat file the same thing happens I loose all digits after the decimal.

|||Are you just going source to destination? No other transformations?|||thats correct.|||Do you receive any truncation warnings when you run the package? (Or ANY warnings?)|||

I don't get any warnings if I use numeric (38,2)

I let the package create the table. The package wants to use numeric (38) but I changed to numeric (38,2) on the create table statement in the destination window.