Corel CTech - Paradox
Diamond Software Group, Inc.
Waldorf, Maryland USA
nospam S. Hirsch skrev:
--Quote:> I have an Access database that I need to import to Paradox. It has a
> a memo field. When I run the import it truncates the memo down to
> a256. Is there a way to avoid losing the data?
Please, no SPAM or Junk Mail
Hello SQL Server Gurus! I am in serious need of some help
as this is driving me absolutely crazy!! In the attached
zip is a Foxpro .dbf file.
Can anyone out there successfully do the following:
1) Import the .dbf into MS SQL Server 2000 (be sure and
save the import as a DTS package).
2) Run that same import (it is saved as a DTS pkg) via a
SQL Server Agent job using the dtsrun command.
Step 1 above works just fine. Step 2, the job fails every
time. Attached is the job's log file showing the error.
Facts: This only happens to me when the .dbf file has a
memo field in it. This dtsrun problem was/is not a
problem on SQL Server 7.
If anyone is successful, please let me know how you did
it. The fact that the manual import works, yet the exact
same import via the SQL Server 2000 job DOES NOT work
seems like a bug to me. VERY frustrating!
Tips for those who want to try:
**You will need to save these 3 files (dbf, cdx, fpt) into
**I use dBase 5 as the data source for the import.
**My dtsrun command in my job step looks like this:
dtsrun /SMyServer /NMyLocalDTSPkg /E
(where "MyServer" is my server name, and "MyLocalDTSPkg"
is my Local DTS Package name)