[AccessD] TransferText Causing System Crash

Thanks for the suggestion.  All the file names have the extension included.

David

At 31/08/2004, you wrote:
>Hi
>
>
>My similar experience with Access(97) running under XP  (with Office XP
>installed) when exporting text data was that if the export text filename
>did not have an file extension e.g. MyDownloadFile, Access would hang.
>Exporting to MyDownloadFile.txt would solve the issue.  May or may not
>be relevant here (I was using Acc 97 but it was the XP OS (or Office XP)
>that seemed to be the issue here).
>
>Richard
>
>-----Original Message-----
>From: David Emerson [mailto:davide at dalyn.co.nz]
>Sent: 30 August 2004 06:26
>To: Access Developers discussion and problem solving
>Subject: Re: [AccessD] TransferText Causing System Crash
>
>That solved most of the problem.  Now the commands work on the server.
>
>However, it is used as a terminal server.  Although it runs fine when
>using
>the program direct on the computer, if anyone connects to a terminal
>server
>session they still get the same crashing.
>
>Any pointers on this one!!
>
>David
>
>At 27/08/2004, you wrote:
> >Oh and one other thing to check that you have installed
> >Overview of Office XP Service Pack 3 for Access 2002 Runtime. Note this
>is
> >in addition to normal SP3
> >http://support.microsoft.com/default.aspx?scid=kb;en-us;834693&Product=
>acc
> >
> >MartyConnelly wrote:
> >
> >>Well it looks like different Office XP service packs on the machines,
>XP
> >>SP-3 on your development machine.
> >>Are you doing a full new runtime install on the server, or just
>passing
> >>over the adp file to the server with changes.?
> >>This could lead to problems.
> >>
> >>David Emerson wrote:
> >>
> >>>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