Will a sole-user, read-only licence be sufficient enough to allow me to convert a QuickBooks 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 QuickBooks application. A sole-user LinkBook licence locks a database exclusively. However, if you do need to concurrently share a QuickBooks database, then you will need a multi-user licence.
I would like to run QuickBooks 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 QuickBooks open to 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 QuickBooks and close and open the ODBC application every time.
A sole-user LinkBook 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 LinkBook up to the licensed number of seats. So, you could have 50 workstations using LinkBook, but only 5 at any one time with a 5-seat licence.
Is there a utility to see how many LinkBook connections are open at a given time?
The LinkBook 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.
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 LinkBook, 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.
I have just tried to install LinkBook 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 LinkBook.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' LinkBook user, in which case you should be OK because the licence file doesn't need to be written again. Although LinkBook.lic only needs creating once, the Registry entries are required on every workstation that might use LinkBook.
Demonstration / Evaluation Default Licence
One of the tables shows no data in Access, whether I use ODBC Import or Link, whereas in QuickBooks there are 19000 records. Could you give me a troubleshooting tip, please?
The evaluation version of LinkBook only lets you 'see' the first 100 records in a table.
We have purchased, and registered, a multi-user LinkBook licence, but still get the default Demonstration / Evaluation licence banner, and we are restricted by the number of records that we can see. Why?
A multi-user LinkBook licence is only valid on a true server network, and may not work on a peer-to-peer network.
If I import a QuickBooks 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 QuickBooks database?
Once tables have been imported into Access - or any other front-end application - LinkBook is no longer required. Only attached tables require the on-going use of LinkBook - this can be appropriate when developing new front-end applications while tables are still being maintained by QuickBooks.
When I import QuickBooks tables, does LinkBook 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 multi-user LinkBook 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 LinkBook 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 LinkBook to access a QuickBooks 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: '[LinkBook] Query Timeout (S1T00)  (#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.
General Application Issues
Does LinkBook correctly identify field types, or is everything of type text?
LinkBook will convert data from
the field type of the QuickBooks field to the requested field type.