[AccessD] TransferText Causing System Crash

I read with interest your recent thread on this one.  Unfortunately in my 
case they are not even running once.

I could rewrite my code so that I read/write in the files line by line (I 
have other code in the same database which does this 
successfully).  However, it would make it much easier if I could get it to 
work again as before.

David

At 26/08/2004, you wrote:
>We've had problems with TransferText (we use TransferSpreadsheet very
>rarely) in AXP mdbs on WinXP Pro and Win2k.  It will run nicely for a
>while and then suddenly blow up entirely.  It appears to be a Jet
>problem, since we're stress testing by handling the same file
>repeatedly, and it goes happily along importing for a while and then
>fails completely.  The interesting thing is that once it fails, the only
>cure is to close the Access session and restart it because TransferText
>won't work even from the code window and you can't do an import from the
>UI either.  We finally resorted to including an automatic restart
>capability in our apps because the fall over point differed between
>machines and each machine seemed to have a magic number of iterations
>before it crashed.
>
>Charlotte Foust
>
>
>-----Original Message-----
>From: David Emerson [mailto:davide at dalyn.co.nz]
>Sent: Thursday, August 26, 2004 4:48 PM
>To: accessd at databaseadvisors.com
>Subject: [AccessD] TransferText Causing System Crash
>
>
>Group,
>
>I have an AXP ade/SQL2000 runtime setup running on Windows 2003
>Server.  When I use the DoCmd.TransferSpreadsheet or DoCmd.TransferText
>commands my database crashes (Unexpected error in MSAccess.exe).
>
>Examples are -
>
>DoCmd.TransferSpreadsheet acExport, acSpreadsheetTypeExcel7,
>strTableName,
>strFullName
>DoCmd.TransferSpreadsheet acImport, , "dbo.ttmpTOURawData", strFullName,
>False DoCmd.TransferSpreadsheet acImport, acSpreadsheetTypeExcel97,
>"dbo.ttmpSwitchNewIn", Me!txtSwitchFile, True DoCmd.TransferSpreadsheet
>acImport, acSpreadsheetTypeExcel97,
>"dbo.ttmpTemporary", Me!txtDataFile
>DoCmd.TransferText acExportDelim, , "dbo.ttmpAgedDebtorDDebitExp",
>strFullName DoCmd.TransferText acExportDelim, , "dbo.ttmpExportMerge",
>DLookup("RootFolder", "tblCompany") & "\Merge\CustMerge.TXT", True
>DoCmd.TransferText acExportDelim, , "dbo.ttmpSwitchNewOut",
>DLookup("RootFolder", "tblCompany") & "\Switch\CustSwitch.TXT", True
>DoCmd.TransferText acImportDelim, , "dbo.ttmpTOURawData", strFullName,
>False
>
>The commands work on my development machine (WXP Professional with
>Office
>97 and Office XP).
>
>I have tried uninstalling and reinstalling the runtime application.
>
>Other commands in the Access library seem to work ok.  The version of
>the
>olb (C:\Program Files\Microsoft OfficeXP\Office10\msacc.olb) on my
>machine
>is 10.0.6308.0.  The runtime machine (C:\Program Files\Microsoft Access
>Runtime\Office10\msacc.olb) has version 10.0.2627.1.
>
>Any clues why the transfer commands might be causing problems?
>
>
>Regards
>
>David Emerson
>Dalyn Software Ltd
>25 Cunliffe St, Churton Park
>Wellington, New Zealand
>Ph/Fax (04) 478-7456
>Mobile 027-280-9348