GOOD NEWS!!!

There is a way to get at the .dbf files w/o trying to use the .dbc (which doesn't work anyway).

There is a program called dbfconverter by HiBase software ... it's 30bucks for the licensed version and it will take the vfp9 dbf's and convert them to a standard .vfp format, so that you can set up your system dsn for ODBC access through crystal reports.

The program has command line functionality, so that you can automate the export/conversion on startup of MSAccess.

BAD NEWS ...
Dydacomp changed the names of some of the fields in the tables ... ex: csm.dbf version 5.4 had the field "order". in 6.0 it's "orderno".

this means that even after you access the files, you'll need to do some debugging of your reporting setup.

HTH

Hi,

I would like to combine duplicate customers without having to do it one at a time in MOM... I have several thousand duplicates... Does anyone have any ideas or know of a way to do this?

Michael

Well, if you have access to presort software such as smartaddresser 2020, or firstlogic's desktop mailer, you could import the customer data, and use the presort software to de-dupe the cust.dbf, then re-import back into MOM ... That's one way that's a thought... Most of these programs will recognise the .dbf format as a matter of course....

another method, if you don't have access to presort software (since it's usually in the 2500 - 6500 USD range is ...

using dbuwin ... export the cust.dbf table to .csv or .xls format, pull it into access (get external data, make new table - dont link, you won't be able to manipulate the data and save changes if you do it that way), sort the table by cust name, address 1, address2, then select and delete the dupe records ...

You MAY ACTUALLY be able to filter out the deleted records somehow by specifiying the requisite filter parameters when you are looking at the file using dbuwin ... but I'm not sure, didn't pay that much attention to it ... I just need to get the dad-blamed ms Access reports back ...

Try the free download below from Microsoft. I'm not sure if it works because I'm not upgrading from MOM 5.4 to 6.0 until a fix for this problem is confirmed by someone other than Dydacomp.

Microsoft OLE DB Provider for Visual FoxPro 9.0
Brief Description
The Visual FoxPro OLE DB Provider (VfpOleDB.dll) exposes OLE DB interfaces that you can use to access Visual FoxPro databases and tables from other programming languages and applications.

http://www.microsoft...;DisplayLang=en

SIGH ... well, that one didn't work either. I did, however, notice some interesting things while trying various combinations of attempts to link tables to an access database...

When linking through a file DSN, whether it's free table database or vfp .dbc, I get the "reserved error -7778 .... no information is provided" error.

When I link through a system DSN, if I use the "free table database" option, all the .dbf files in momwin that have an associated .cdx file are hidden and I can't access them. The ones that DON'T have an associated .cdx file, however, are available for access. I didn't try to access them, cause they're not the ones I need (woudn'tcha know ...)

When I link through a system DSN and use the vfp .DBC option, I get the "not a table" error. Perhaps this might help someone help me find a solution. I have a client who runs daily reports from ACCESS and hasn't been able to do so for a week now, since upgrading to MOM6.