Charlotte Foust
charlotte.foust at gmail.com
Tue Apr 19 20:15:41 CDT 2011
I'm not sure this is an Access issue. I seem to recall that the # sign has a specific meaning in passing data into and out of delimited text file. Maybe someone else can recall the specifics. You might be able to work around it by either using a double # in the export spec for the field name, or else export and then rename the field in the csv file using text IO code. Charlotte Foust On Tue, Apr 19, 2011 at 3:23 PM, Brad Marks <BradM at blackforestltd.com> wrote: > All, > > We are just starting to use an Access 2007 application to feed data to > another outside system via a CSV file. > > This outside system is very rigid and we need to use exact field names > on the CSV file that we are creating. > > The catch is that one of the fields is call "Employee #". > > We set up an Export Specification (called Export-Query1 for our testing) > and we are using the following command to do the export > > DoCmd.RunSavedImportExport "Export-Query1" > > When we run the application, everything works nicely, except the field > named "Employee #" is somehow being renamed "Employee ." in the > generated CSV file. > > We have run a number of tests and it looks like we have stumbled upon > either a "bug" a "feature", or something that we just don't understand. > > Is there a way to force Access to not replace the "#" with a "." ? > > Thanks for your help, > > Brad > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >