Frequently Asked Questions?

LinkEase Licence Options

We currently use ConnectEase and are looking for a more robust product. How can we get an unlimited version of LinkEase to test it out on some very large files? A time-limited version for a week or so would be very helpful.

We are pleased that you are looking at LinkEase as a more robust alternative to ConnectEase. We cannot guarantee that LinkEase is bug free - what software is - but we do guarantee to respond quickly to any problems you encounter and will fix any LinkEase failures to implement our advertised level of ODBC compliance. All versions of LinkEase are fully supported!

Many clients only use LinkEase to transfer data from a DataEase database into some other front-end application, such as Access, and a time-limited version of LinkEase would allow them to carry out this task without having to pay a licence fee. Licence fees fund support and future development. For this reason, such versions are not made available.

The default Demonstration / Evaluation LinkEase licence lets you 'see' all the columns in the first 50 records of all tables. A 1-seat, sole-user, read-only LinkEase licence only costs £UK180 ($US290), enables full access to all your tables, and should allow you to carry out your extended evaluation.

Will a sole-user, read-only licence be sufficient enough to allow me to convert a DataEase database into Access, or will I need a multi-user licence?

A sole-user licence will allow access to a database on a network drive as long as it is not being used by another DataEase application. A sole-user LinkEase licence locks a database exclusively. However, if you do need to concurrently share a DataEase database, then you will need a multi-user licence.

If I buy a 5-seat licence - will running DataEase "take up" one of the seats? Or can I run 5 ODBC users and 50 DataEase users at the same time?

DataEase does not take up any LinkEase licence seats. You would be able to run 5 ODBC users and 50 DataEase users. However, some applications open more than one connection at a time, and each LinkEase connection takes one licence seat. e.g. If you use Access to view tables in 2 different DataEase databases at the same time, 2 seats will be used.

I would like to run DataEase at the same time as I am running an ODBC application. But when I try this, I get a "Key violation .... Unknown Database" - error message. Is this due to the fact that I have a sole-user licence, and would I have the same problem if I had a multi-user licence? I need this functionality because I need DataEase open to run some DQL's, and copy some data into a table the ODBC application reads. This can be done many times before the user is satisfied, and it would be nice if the user didn't have to close and open DataEase and close and open the ODBC application every time.

A sole-user LinkEase licence locks a database exclusively and will not share data with other users. I do not expect a "Key violation" error, but you should get some error. A multi-user licence would resolve this problem.

Can a 5-seat licence be spread over multiple PC's - or will the licence have to be "bound" to specific computers?

A multi-user licence resides on a network drive and allows any number of workstations to concurrently use LinkEase up to the licensed number of seats. So, you could have 50 workstations using LinkEase, but only 5 at any one time with a 5-seat licence.

Is there a utility to see how many LinkEase connections are open at a given time?

The LinkEase release zip file contains a DOS utility, licences.exe, that you can run in a DOS window to report the number of licence seats currently used.

Installation Issues

Where does LinkEase get installed - on the DOS machine or the Windows machine where we're running Access?

You cannot use LinkEase on a DOS machine. LinkEase should be installed on the Windows machine where you want to run your front-end application, such as Access, that needs access to your DataEase database. The database must reside either on the same Windows machine or on an accessible drive on your network.

I am investigating extracting data from DataEase into an SQL database and have downloaded the trial version from your web site. This installed OK and after setting up a Data Source for a DataEase 4.53 database, I tried to connect using Borland's Database explorer. At which point the splash screen is displayed followed by the error message 'System Error in DP_open_database [23231]'. Any idea what could be causing this? Would this happen with the production version also? I am running on Windows 98.

The error number indicates that LinkEase failed to find the NetWare API library, CALWIN32.DLL, which it needs. This is usually loaded automatically when you install the Novell NetWare Client. The Microsoft client for NetWare is not recommended for DataEase databases and will not function with LinkEase. The production version will return the same error. You can download the appropriate client by visiting the Novell Download Site and selecting Client v3.1 for Windows 95/98 English.

How soon will I receive the software?

You already have the software which you downloaded from our web site. To benefit from the full functionality of LinkEase, all you need is a licence file which can be supplied once you have provided an official order and sitecode file. The process is documented in a Word 6 file that you can also download from our web site.

How does the driver knows where to look for the licence? Should I have installed it in the main DataEase directory? I am running NT4, if that helps, and don't have any DataEase environment variables except when I run our DataEase application.

When you run register.exe on a workstation, it both creates the LinkEase.lic file in your licence directory and adds entries to the workstation Registry that LinkEase uses to find the licence file.

Why am I getting the error message 'System File is Missing in DP_open_database (11114)'?

This error is caused by a missing file, ztermdef.dbz, which LinkEase expects to find in the DataEase directory. Since you have had Access working before, I suspect that this problem is caused by having an incorrect Data Source Name specification with DataEase directory pointing to the wrong place.

Why are we are getting: 'System Error in DP_open_database [18333]?

This error indicates that LinkEase cannot open CONFIGUR.DAT which it expects to find in the directory pointed to by the DEPATH environment variable, or the DataEase directory.

We are getting the following error: 'System Error in DP_open_database [21164]?

This error indicates that LinkEase cannot open DENETWRK.OVL which it expects to find in the directory pointed to by the DEPATH environment variable, or the DataEase directory.

I have just tried to install LinkEase onto a second machine, also NT workstation, Novell client installed. I have run the setup program and then tried to run register. It gives me an error message "Cannot create LinkEase.lic" when I press the OK button. I have pointed the "licence directory" to the same network directory as my machine. Could you point out where I'm going wrong?

You may not have write rights for the licence directory with the username on the particular workstation. Or, the licence file may already be locked by another 'live' LinkEase user, in which case you should be OK because the licence file doesn't need to be written again. Although LinkEase.lic only needs creating once, the Registry entries are required on every workstation that might use LinkEase.

Why am I getting a Windows Warning Message Box (Title DEPATH) : "Environment variable NOT set in DP_open_database (21161)" followed by an Access message that the ODBC call failed and finally a report "LinkEase Error 81000 [40123] (-90): Reported Fatal System Error [21161] (#-90)"?

The error that you are getting is consistent with the environment variable DEPATH not being set to a valid value. LinkEase does not require DENAME, but it does require DEPATH to maintain access locking integrity with other DataEase users of a database on a non-Novell network. Registry entries are required on every workstation that might use LinkEase.

Do you have an error code cheat sheet?

The first part of the error code, e.g. S1000, is a Microsoft specified code that is documented in any respectable ODBC manual, though many of them are generic and don’t, by themselves, help very much. This is especially so when setting up LinkEase because of the complex environment dictated by DataEase. You might also find this Frequently Asked Questions page covers the most common error situations. The 5 digit number in square brackets points to the LinkEase code location that generated the error. There are hundreds of possible error locations, though most are rarely, if ever, seen. As you develop your interface, errors are then generally caused by faulty SQL syntax and ODBC documentation is more helpful.

The only error code location ‘cheat sheet’ that we have lists the range of error locations contained in code modules which would not help you, but does help us to locate the code and suggest a cause.

Demonstration / Evaluation Default Licence

One of the DataEase tables shows no data in Access, whether I use ODBC Import or Link, whereas in DataEase there are 19000 records. Could you give me a troubleshooting tip, please?

The evaluation version of LinkEase only lets you 'see' the first 50 records in a table. Some or all of the first 50 records may be marked as deleted. Try reorganising the table to remove deleted records. Alternatively, you may have logged on to the database with a username / password that does not allow access to records or columns in that table.

We have purchased, and registered, a multi-user LinkEase licence, but still get the default Demonstration / Evaluation licence banner, and we are restricted by the number of tables, records, and fields that we can see.  Why?

A multi-user LinkEase licence is only valid on a true server network, and may not work on a peer-to-peer network.

Microsoft Access

If I import a DataEase database into Access and not just attach it, will I then be able to save the Access version (complete with imported tables and data) onto another computer and be able to read and write to the tables, or will I still need to use the original dataease database?

Once tables have been imported into Access - or any other front-end application - LinkEase is no longer required. Only attached tables require the on-going use of LinkEase - this can be appropriate when developing new front-end applications while tables are still being maintained by DataEase applications.

When I import DataEase tables, does LinkEase also import all the data or just the table structure and will it allow me to save the resulting Access database under a different folder?

Access imports both a table's structure and data, but not relationships. The resulting Access database can be moved to a different folder.

We have a 5-seat, multi-user, read-write LinkEase licence, but keep running out of licence seats when just two users are logged on. We are using the driver in some MS Word and Access applications which work well other than this problem. I think MS Jet somehow caches the drivers and we have to tell the users to unload the MS Office application to release a seat. However the LinkEase licence file is only open by two users at the time.

A seat is used every time an application calls SQLAllocConnect, and released with a call to SQLFreeConnect. Some applications can call SQLAllocConnect more than once before calling SQLFreeConnect. Your problem is caused by MS Word or Access not freeing a connection when a user has finished using LinkEase to access a DataEase database. Closing an application frees its connections and releases the seats. You can download two Microsoft White Papers, Jet Database Engine ODBC Connectivity (16-bit versions of Access) and Jet Database Engine Version 3.0: ODBC Connectivity (32-bit versions of Access), which could help a little with the background to your problem. You can change the default ConnectionTimeout parameter from 258 (600) [seconds] to another more appropriate value (in the Registry at [HKEY_LOCAL_MACHINE][SOFTWARE][Microsoft][Jet][n.m][Engines][ODBC]), where n.m is 3.5 for Access 97 and 4.0 for Access 2000.

When opening a table from the Access Database Window and navigating through a large table, the following messages appear after about 60 seconds: 'ODBC call failed', followed by: '[LinkEase] Query Timeout (S1T00) [38166] (#0)' . Then the form fills with #Name? entries and I have to close the Window and start again. Is this a design feature?

This is a typical problem with large tables and Access. Access sets a default timeout of 60 seconds for any query which an ODBC driver must obey and return the S1T00 error if the query cannot be completed within the given timescale. You can download two Microsoft White Papers, Jet Database Engine ODBC Connectivity (16-bit versions of Access) and Jet Database Engine Version 3.0: ODBC Connectivity (32-bit versions of Access), which could help a little with the background to your problem. You can change the default Query Timeout parameter from 3c (60) [seconds] to another more appropriate value (in the Registry at [HKEY_LOCAL_MACHINE][SOFTWARE][Microsoft][Jet][n.m][Engines][ODBC]), where n.m is 3.5 for Access 97 and 4.0 for Access 2000.

I changed the Registry Query Timeout parameter, but I still get an S1T00 error when running an Access Query?

Every Access Query also has it's own ODBC Timeout property (60), which should be set to a sufficiently large value.

When linking a table to Access 97, I get the following error message: "The database engine can't find '<table name>'". When importing the same table, I get the following error message: "The database engine can't find 'VtQoDefTemp0000'". Any ideas?

These errors can occur when you attempt to link or import a DataEase table that has field names containing invalid Access characters, such as the '.'. If you replace each invalid characters with a different acceptable character (e.g. '_') as per the instructions in the Data Source Name setup section of the LinkEase documentation, this problem will be resolved.

When I link a table to Access 97 and then open it, I get "#Deleted" in every field?

This error can occur when you attempt to link a DataEase table that has field names containing invalid Access characters, such as '='. If you replace the each invalid character with a different acceptable character (e.g. '^') as per the instructions in the Data Source Name setup section of the LinkEase documentation, this problem will be resolved.

I replaced both '.' and '=' with '_', but now I get "#Name?" in every field?

You have to translate each invalid character into a different alternative! Otherwise, LinkEase cannot determine what the original character was, and so cannot re-construct the original DataEase field names, when it is asked to retrieve data. You could replace '.' with '#', and '=' with '^', or some other different characters.

General Application Issues

Why can't PowerBuilder read a DataEase database table, 'adjuster details', using LinkEase? I have included an ODBC Trace and a copy of the database.

I have completed my analysis of the ODBC trace file by testing some of the ODBC calls against the database that you sent me. I have concluded that PowerBuilder is not complying with the ODBC specification on several counts:

PowerBuilder makes an SQLGetInfo call to LinkEase with a parameter of SQL_ODBC_API_CONFORMANCE which returns 1 (SQL_OAC_LEVEL1). This advises PowerBuilder that LinkEase will only accept Core and Extension Level 1 API calls. PowerBuilder later makes calls to SQLPrimaryKeys and SQLForeignKeys which are both Extension Level 2. This in itself may not be important if PowerBuilder takes the error result returned as confirmation that the function calls are not supported.

PowerBuilder then makes a call to SQLStatistics, giving a table name of 'adjuster'. However the length is given as 16 and coincidentally 'adjuster details' is 16 characters long. It looks as though PowerBuilder has turned the space into a NULL. LinkEase tries to find the table 'adjuster' and gives the correct response when it fails to find it.

Power builder then makes a call to SQLExecDirect with an SQL statement of 'SELECT adj FROM adjuster details'. LinkEase parses the SQL statement and takes 'adjuster' as the table name and 'details' as its correlation name in conformance with the ODBC specification. The SQL statement should have read 'SELECT adj FROM "adjuster details" ', so that 'adjuster details' is taken as the table name. PowerBuilder should have asked LinkEase for SQL_IDENTIFIER_QUOTE_CHAR via a call to SQLGetInfo and used the returned character to enclose the table name. Again, LinkEase tries to find the table 'adjuster' and gives the correct response when it fails to find it.

Your problem appears to be caused by PowerBuilder not handling embedded spaces in table names correctly. My advice is to use the Options section in the LinkEase - ODBC Driver for DataEase Setup dialog box that you get when you are maintaining your Data Source Name. Use the two column table to replace spaces by another character, say an underscore (_).

Does LinkEase use the numeric or text values when retrieving data from DataEase Choice fields?

It depends on whether you request a text or a numeric value. Applications, such as Access, tend to ask for a text value which LinkEase then supplies.

Does LinkEase correctly identify field types, or is everything of type text?

LinkEase will convert data from the field type of the DataEase field to the requested field type.

Why can we not see every field in a form?

LinkEase will not include those fields that have Prevent Data-entry set to 'Virtual' or Prevent Data-entry set to 'Yes' and no Derivation Formula.

Why can we not see every form?

LinkEase will not include those forms in which every field has Prevent Data-entry set to 'Virtual' or Prevent Data-entry set to 'Yes' and no Derivation Formula.

We have tried to import a table from a DataEase database into Access through LinkEase and it worked fine. Why do we get a problem when we use Crystal Reports with LinkEase? I have included an ODBC Trace.

LinkEase has had some difficulty scanning the syntax of the SQL query sent by Crystal Reports. The SQL code sent, 'SELECT Order."ORDERTYP", Order."Datum" FROM "Order" Order ORDER BY Order."ORDERTYP" ASC, Order."Datum" ASC', is probably causing some confusion because of the use of the keyword 'order' in different contexts. 'ORDER' is defined as a reserved word in the ODBC specification. The ODBC Trace shows that LinkEase is compatible with Crystal Reports as long as you don't have table names that are in the reserved word list. Another possibility is to temporarily replace R with Z, or something similar, in the DSN configuration so that Crystal Reports is persuaded that the table name is OZDEZ?!?

We have a 30-seat licence. There are 2 developers. We have implemented a NetPlus application that is being used by 6 users. The application displays information from only one DataEase database at a time. It seems that the connections are not being dropped and soon add up to our 30-seat licence. When we close the NetPlus application, then the connections seem to be dropped.

NetPlus applications do not release connections to DataEase databases through LinkEase until the applications close. Even though the applications are only displaying data from one database at a time, each new database uses another seat until your licenced seats are exhausted.

HomeEmail Us