dameng
Senior Member
  

DBA / EVO Software Consultant
Posts: 275
Gender:
|
the DDF's that are designed to be used with the ODBC, do NOT contain the extensions, they only contain the File ( hence Table ) name. if you incorrectly used the DDF's that are in the Root dir of DBAMFG, which are only for use by Maintain Database, those DDF's DO List the files WITH their extensions. consequently, use the ODBC for both read and write access. also, the DDF's again in the Root of DBAMFG, correctly show the original file / field structure, which are those Field Names that the programmer did use [ ] for multiple instances of the same name/type field. ( old programming technique...) the DDFs that are used for ODBC, have corrected that idiosyncracy, by omitting the [], and substituting the underscore _ . i think you are using the wrong DDF's for your development connection. since you listed the BKARINV_BNB table. the ODBC would only list that as: BKARINV since the DDF's would reside in the same directory as your *.BNB files. also, an added side note, it's not recommended to write back to the database. however, if you do, "push" data back in, make sure you follow the same logic that the software follows, as if the user had entered the data in the appropriate entry screen in the software. if not, there will be problems with data information not sync'd. to create the proper DDF's for your specific company. make sure you are logged into DBA or EVO, in the NB company, go to Utilities on the System Manager menu, UT-A run a DBA program, type in ODBCDDF.RUN then on your server, create a SYSTEM DSN that points to those DDF's in the NB directory. then on your Client workstation, create a SYSTEM DSN that points to your Server's DSN. then if you use the pervasive development tools, oledb, or create your own db connection string, you can choose to use the odbc, rather than specifying the full db server connection. either way, you do need to use those DDF's that are ODBC compliant. HTH, dave
|