AnsweredAssumed Answered

Import broken, unsupported format with dbase file with non standard extension (*.env)

Question asked by philmee95 on Apr 11, 2012
Latest reply on Apr 11, 2012 by rmanook

Summary

Import broken, unsupported format with dbase file with non standard extension (*.env)

Product

FileMaker Pro

Version

12

Operating system version

Windows, will trya mac later

Description of the issue

Try to impport a file with non supported extension, but supported type. The file is text and is exported as an industry standard to automotive bodyshops. The exported file is called EMS extract. Importing this file works fine in Filemaker up to this latest version.

There should not be filters like this built into filemaker. It is a text file. We process hundreds of records a day and can't go rename 20 files for each "record" that we export as 20 files are exported as a result of EMS extract which is an automobile collision standard. We have many programs that use it to exchange data (ccc pathways, mitchell ultramate and insurance company reporting and data exchnage apps).

http://ccc.cccis.com/pages/ccc_autoverse__repair_management/67.php
CIECA standard Estimate Management Standard

dbase is listed as supported in fmp 11
http://www.filemaker.com/11help/html/import_export.16.24.html

Steps to reproduce the problem

rename a dbase file with any random extension like "env" and try to import.

Expected result

the file should be imported like dbase as it contains text, not binary.

Actual result

"the file could not be translated using the selected file type."

Failure.

Exact text of any error message(s) that appear

"the file could not be translated using the selected file type."

Configuration information

win7 64, win7 32, win xp

Workaround

use filemaker 11 advanced server and pro and advanced for now.

Outcomes