You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Nattanicha (JIRA)" <ji...@apache.org> on 2008/09/01 11:43:44 UTC

[jira] Created: (OFBIZ-1941) fieldtypevisualfoxpro.xml

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


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 jdbc-odbc bridge 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.


[jira] Commented: (OFBIZ-1941) fieldtypevisualfoxpro.xml

Posted by "Nattanicha (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OFBIZ-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627579#action_12627579 ] 

Nattanicha commented on OFBIZ-1941:
-----------------------------------

Bruno,

I will upload patch soon, Thank you.

> 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: 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.


[jira] Commented: (OFBIZ-1941) fieldtypevisualfoxpro.xml

Posted by "BJ Freeman (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OFBIZ-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629112#action_12629112 ] 

BJ Freeman commented on OFBIZ-1941:
-----------------------------------

Yes now you have entityengine.xml setup  you can go to the page I gave you the link to, and use it to created you entity models from your foxpro db you have set up in the entityengine.xml
bye default they will fit your fieldtypevisualfoxpro.xml, since they are taking them from the DB directly.


> 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.


[jira] Updated: (OFBIZ-1941) fieldtypevisualfoxpro.xml

Posted by "Nattanicha (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OFBIZ-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nattanicha updated OFBIZ-1941:
------------------------------

    Description: 
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.

  was:
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 jdbc-odbc bridge 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.


> 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: 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.


[jira] Updated: (OFBIZ-1941) fieldtypevisualfoxpro.xml

Posted by "Nattanicha (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OFBIZ-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nattanicha updated OFBIZ-1941:
------------------------------

    Attachment: fieldtypevisualfoxpro.xml

fieldtypevisualfoxpro.xml by Nattanicha Rittammanart and Bruno Busco

> 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: 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 jdbc-odbc bridge 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.


[jira] Updated: (OFBIZ-1941) fieldtypevisualfoxpro.xml

Posted by "Nattanicha (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OFBIZ-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nattanicha updated OFBIZ-1941:
------------------------------

    Attachment: entityengine.patch

patch for entityengine.xml to work with fieldtypevisualfoxpro.xml

> 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.


[jira] Commented: (OFBIZ-1941) fieldtypevisualfoxpro.xml

Posted by "Nattanicha (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OFBIZ-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627578#action_12627578 ] 

Nattanicha commented on OFBIZ-1941:
-----------------------------------

Sorry if I confused all of You. My objective for this issue is about INTEGRATION. So, it does not mean that I need Foxpro to be one of databases (among many databases that are provided to use with OFBiz, for example, derby, mysql and postgresql) that can be connected and put all of OFBiz data. I just need OFBiz to provide entity configuration to connect with DBF file.

This issue came from my experience when I created new application on OFBiz and this new one need to be connected with Foxpro. The most important problem that I faced is there is no entity definition for Foxpro database. I cannot create entity to connect with existing DBF file. I need to find the way to do it with myself. Many people in Thailand also faced this problem (but I don't know how about others). So, if the entity configuration and approach to connect Foxpro can be provided into default OFBiz, it should be the most appreciated. We can use our new application with Foxpro that can be integrated with other applications in OFBiz which are connected other databases.

I can find the approach to do this by creating fieldtypevisualfoxpro.xml, modified entityengine.xml and using Visual Foxpro ODBC. Moreover, I faced that this way can be used only in Windows, I have plan to develop JDBC for foxpro database.

Anyway, when I created my new application, I created entity model. I need to put no time stamp because I don't need it create new variables about time stamp into DBF file (that longer than 8 characters). So, I cannot put enable-lock=true because I don't have time stamp variables created in. The way I done this is I modified variables in ModelEntity.java about time stamp to be not longer than 8 characters, then I can use my new application that can be connected to DBF that is provided lock machanism. This is not a good way because I changed the static variables inside ModelEntity.java. That's why I need to ask about this solution.

> 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: 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.


[jira] Commented: (OFBIZ-1941) fieldtypevisualfoxpro.xml

Posted by "Jacques Le Roux (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OFBIZ-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627455#action_12627455 ] 

Jacques Le Roux commented on OFBIZ-1941:
----------------------------------------

Hi Nattanicha,

As BJ already pointed ou in ML this would be barely usable as you mentionned in user ML

{quote}I must modify variables in ModelEntity.java because Foxpro cannot uses fields names that are longer than 8 characters.{quote}

and above

{quote}Foxpro need to be put no-auto-stamp="true" for entity because Foxpro does not support variable name that is longer than 8 characters.{quote}

This last comment is not clear to me. Do you mean that only field names (DB columns) can't be longer than 8 characters or other DB elements (relations names, indexes, etc.) are also concerned ?

I don' t close this issue for now in case someone has a solution or ideas. But unfortunately I guess this is what will happen because we would need to have a complete rewritting of entities definitions. Of course if you provide this rewritting we could propose a patch for possibly other/future users but it will never be commited in OFBiz and would have to be updated as the data model is not freezed...

> 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: 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.


[jira] Commented: (OFBIZ-1941) fieldtypevisualfoxpro.xml

Posted by "Nattanicha (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OFBIZ-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629106#action_12629106 ] 

Nattanicha commented on OFBIZ-1941:
-----------------------------------

Oh, sorry for my wrong type. I mean I changed entityengine.xml a little bit (entityengine.patch), not entitymodel.xml.

> 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.


[jira] Commented: (OFBIZ-1941) fieldtypevisualfoxpro.xml

Posted by "BJ Freeman (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OFBIZ-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629100#action_12629100 ] 

BJ Freeman commented on OFBIZ-1941:
-----------------------------------

Best practices is you don't change the Entity unless you have to.
I was showing you a way to create new entities for you db without making changes to the Entities Model.
it was a suggestion, not a direction.



> 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.


[jira] Closed: (OFBIZ-1941) fieldtypevisualfoxpro.xml

Posted by "Adrian Crum (JIRA)" <ji...@apache.org>.
     [ 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.


[jira] Commented: (OFBIZ-1941) fieldtypevisualfoxpro.xml

Posted by "Bruno Busco (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OFBIZ-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627428#action_12627428 ] 

Bruno Busco commented on OFBIZ-1941:
------------------------------------

Nattanicha,
you should also attach a patch to the framework/entity/config/entityengine.xml file.
Here you could put a commented code segment that will show how to connect to VFP (replicating what exists for the others).
If you don't know how to create a patch please refer to: http://docs.ofbiz.org/display/OFBADMIN/OFBiz+Contributors+Best+Practices


> 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: 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.


[jira] Commented: (OFBIZ-1941) fieldtypevisualfoxpro.xml

Posted by "Nattanicha (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OFBIZ-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629072#action_12629072 ] 

Nattanicha commented on OFBIZ-1941:
-----------------------------------

Dear BJ Freeman,

Instead of creating entity model by using webtools, I modified entitymodel.xml a little bit. Then I could work with fieldtypevisualfoxpro.xml. Or you still want me to do it in webtools?


> 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.


[jira] Commented: (OFBIZ-1941) fieldtypevisualfoxpro.xml

Posted by "BJ Freeman (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OFBIZ-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627617#action_12627617 ] 

BJ Freeman commented on OFBIZ-1941:
-----------------------------------

if I understand you, you want to create a entity model from your database.
the only step I have not seen is using the webtools to generate you entity models from the database
https://demo.hotwaxmedia.com/webtools/control/view/ModelInduceFromDb
created them from the table definition of the db.

all the code for this is in
framework\webtools\webapp\webtools\entity\ModelInduceFromDb.jsp


> 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: 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.