Recent content by Seabz420

I have no control over how the source tables are setup, nor do I have access to them (outside of data retrieval). I've mananged to work around the issue (by going in a completely different direction with this) but I'll keep all this in mind as our sister organizations will eventually run into this.

You are correct, which makes this seem strange as I'm told that the source field is really (2,0) yet SQL is trying to read it as (2,4).

OK, the data that I need to store are numbers ranging from 100,000,000,000 to 300,000,000,000. That pretty much rules out using any type of numeric data type, correct? It still doesn't explain why varchar doesn't work though.

So I tried to take the source data and import it into a txt file using SQL 2000 but even that errors out!

Do you think something like this may be the issue here? http://donxml.com/allthingstechie/archive/2006/01/05/2410.aspx

Still receive the same error message. The table gets created just fine but then it errors out when it tries to transfer it. One question is what is length in reference to Scale and Precision? The length doesn't seem to change when I change the other two, unless I make a drastic change to...

Well, I tried the same datatypes but it wouldn't work so I figured SQL needed to transform the data to something else... When I made a DTS to create the table and import the data, the fields were created with the same datatypes as the source and it still didn't work.

Mutley, I've checked the data over and no null or empty values exist. I suspect a datatype issue but similiar numeric fields in other tables transform to nvarchar just fine. To just test it, is there a datatype that will work for sure (either char or something..not char because it doesn't work...

SQL Server 2000 I have a DTS that just copies the data from one database to the SQL server. No custom code involved. This works for all 69 other tables but this one table is giving me the error: "Error at Source for Row number 1. Errors encountered so far in this task: 1. Multiple-step OLE...

Here's what I managed to get from the SQL help.. USE master EXEC sp_addumpdevice 'disk', 'XX_Backup', 'D:\XX_Backup.bak' BACKUP DATABASE XX TO XX_Backup I created a DTS package with an Execute SQL command with this in it and it works.

I should have been more specific. The backup is of one database. Each month we receive, from our parent company, data that we upload to SQL and we take the old data and archive it. We've now worked it so SQL will directly connect to the parent DB and import the data (using DTS packages). Now...

SQL Server 2000 Is it possible to trigger a backup from a DTS package? I need to perform a backup once a month but the dates vary so scheduling won't work. Also, it needs to be dummy proof so for someone to just trigger the DTS which could trigger the backup would be ideal. Thoughts? Thanks...

This worked for me. thread705-1102193

I have a form with a cmd button that imports data from another DB into my DB. I'm not to DB VBA coding so here is what I have (which works for one table): DoCmd.TransferDatabase acImport, "ODBC Database", "ODBC;DSN=XXXXXXXXXX", acTable, "DB1Table", "DB2Table", , False Now, I have over 100...

Ah lbass, so simple a solution yet so troubling a problem! On the Sub Report link, I hadn't selected the two different formula fields (easly missed as they were named the same). I renamed the formula fields (1 and 2), relinked the subreport properly and everything works fine now. Thanks for...