[
https://issues.apache.org/jira/browse/OFBIZ-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrian Crum closed OFBIZ-1941.
------------------------------
Resolution: Won't Fix
I'm closing this because there are good reasons against doing things this way.
Anyone needing a Foxpro compatible fieldtype.xml file can use the
fieldtypeadvantage.xml file. The Advantage database is Foxpro compatible.
OFBiz itself will NOT run on Foxpro - the Foxpro DBF format has too many
limitations that make it impossible. It is possible to share existing Foxpro
tables with OFBiz. Anyone wanting to know how to do that can contact me.
> fieldtypevisualfoxpro.xml
> -------------------------
>
> Key: OFBIZ-1941
> URL: https://issues.apache.org/jira/browse/OFBIZ-1941
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
> Environment: Windows, JDBC-ODBC bridge
> Reporter: Nattanicha
> Priority: Minor
> Attachments: entityengine.patch, fieldtypevisualfoxpro.xml
>
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> Normally, OFBiz provides many field type files in framework\entity\fieldtype
> that can be used with many types of database. Visual foxpro is also a
> database type that need to be used to connect with OFBiz. Many legacy systems
> was developed by using Foxpro and need to be connected to new ERP system.
> By using fieldtypevisualfoxpro.xml, users must use Visual Foxpro ODBC driver
> (http://msdn.microsoft.com/en-us/vfoxpro/bb190233.aspx) to be a driver to
> connect with DBF file because I cannot find DBF JDBC driver for free. Anyway,
> entity creation in entitymodel.xml for Foxpro need to be put
> no-auto-stamp="true" for entity because Foxpro does not support variable name
> that is longer than 8 characters. This problem should be fixed later if we
> need to use foxpro in OFBiz with Locking.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
