Rocky Smolin
rockysmolin at bchacc.com
Thu Oct 27 09:57:48 CDT 2011
I'll second the VBA approach. I have used it several times because of the unreliability of the Transfer functions - TransferText, TrasferSpreadsheet, etc. It's not very much code and you have complete control - build the string and output it to your file using Print #. Rocky Smolin Beach Access Software 858-259-4334 www.bchacc.com www.e-z-mrp.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Debbie Sent: Thursday, October 27, 2011 6:02 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Tab delimited text file The line by line method is definitely in consideration. I was hoping for something that would be a little more friendly to the user who developed this db. You never know when someone on this list has the perfect elegant solution. Debbie Sent from my iPhone On Oct 27, 2011, at 7:01 AM, Arthur Fuller <fuller.artful at gmail.com> wrote: > That looks like a cleaner solution than my clumsy external method. > A. > > On Thu, Oct 27, 2011 at 7:56 AM, Paul Hartland > <paul.hartland at googlemail.com >> wrote: > >> Could you not write a function to export the file line by line, put >> the file into a recordset, open a text file for exporting to and loop >> through the recordset and print each line into the file using >> something like >> >> Print #FileNumber, YourRecordset.GetString(, , vbTab, vbCrLf, ""); >> >> Has worked for me in the past. >> >> > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com