MS Access 2007 Import Problem

[Matt Sherrill]

Kenneth,
     I'm guessing one of the myriad Microsoft updates changed MS Office - which changed Access.

I'm going to try to fix it your way on the export.  Currently the field edit is setup as "nn,nnn,nnn,nnn".  I'm going to see if I can change it to NOT include the commas.

Thanks,

Matt




________________________________
 From: Kenneth Brody <kenbrody at spamcop.net>
To: Matt Sherrill <mmsv45 at yahoo.com> 
Cc: "filepro-list at lists.celestial.com" <filepro-list at lists.celestial.com> 
Sent: Monday, May 13, 2013 2:45 PM
Subject: Re: MS Access 2007 Import Problem
 

On 5/13/2013 2:10 PM, Matt Sherrill wrote:
> Hi All!
>
> For years, I've been using an Access Macro to import a FilePro exported
> text file to a predefined table.  Now all of a sudden, Access errors out
> on all numbers that have a comma in them.
>
> Nothing has changed.  There doesn't seem to be any difference if I
> manually import the text file, or use a Macro.
>
> Upon completion of the Access Import, any number with a comma fails to
> import (Type Conversion Failure).

Well, obviously *something* has changed.

Have the filePro numbers always had commas in them? Have you upgraded Access 
recently?

[...]
> Either I need to fix the Access Import procedure or figure out a way to
> export the FilePro number fields - without - commas.
>
> I can't change the definition of the FilePro number fields.
[...]

Well, without knowing anything about your file or the export, I can tell you 
that you can eliminate the commas from the fields by using DOEDIT() to 
convert the number to a non-comma version.

For example, if you have a ",2" field, you could convert it to a ".2" using 
something like:

Change

     myexport(3) = ytd_sales

to

     myexport(3) = doedit(ytd_sales,".2")


-- 
Kenneth Brody
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20130513/ebc63dc9/attachment.html