Purchase From Software House
Home
Logic Works

Index of Topics


TECH SUPPORT

What are the Logic Works Technical Support hours?
Logic Works Technical Support hours are Monday to Friday, 9 AM to 7 PM, Eastern Time.

How do I contact Logic Works Technical Support?
Telephone: 1-609-514-2020
Fax:
1-609-514-2869
CompuServe Forum:
GO LOGICWORKS
Internet e-mail:
SUPPORT@LOGICWORKS.COM
CompuServe e-mail:
7062,1135
Web Home Page:
http://www.logicworks.com


INSTALLATION

How can I get and use an evaluation copy of TESTBytes?
First call your Sales Associate at 1-800-783-7946 they will give you a key code. Once you download it off of our web sight you install the program. Then go to the license manager and put in the key code and be sure that the path to TESTBytes is in the key code directory as well.

Which number is my serial number, and where is it located?
TESTBytes users will be prompted for the serial number at installation time. The serial number for Logic Works' TESTBytes products can be found on a square label with a bar code printed on it. The label can be found on the side of the box, the back cover of the Users Guide, and on the registration form. The actual serial number is the number immediately below the code. After installation, the serial number can be accessed by choosing Help | About from the main TESTBytes pull down menu.

How does TESTBytes connect to my Database?
Connecting to the various DBMSs comprise the largest category of questions to Logic Works Technical Support. TESTBytes connects to your database via ODBC standard drivers, and setting up a datasource through the ODBC Administrator.

Does TESTBytes include connection software?
TESTBytes like most SQL enabled products, relies on external software to connect to your DBMS. Because TESTBytes supports many different DBMSs, because each DBMS may have several methods of connection (each with different advantages and disadvantages), because most connection software is proprietary, and because many shops already own the connection software necessary to connect to their DBMS, TESTBytes itself does not ship with connection software for supported databases. TESTBytes also only connects via ODBC.

How do I install the connection software?
Use the install program supplied by the manufacturer of the client connection software. Like most Windows software, trying to make it work by simply copying files to this or that directory in response to error messages is almost always frustrating and ineffectual.

Where can I get the ODBC drivers from?
ODBC drivers may be obtained from your DBMS manufacturer, Microsoft, or third party driver manufacturer such as Intersolv.

Which DBMSs does TESTBytes support? And which ODBS Driver Version should I use?
TESTBytes supports Oracle, Sybase, Informix, DB2, SQL Server and other ODBC-compliant databases.

The following chart provides a summary of the connection software certified for running TESTBytes with each DBMS. However, it is possible that you will encounter no difficulty using alternative drivers.

DBMS

Connection Software

SQL server 6.0 & 6.5

Microsoft SQL Server 2.5

Intersolv 2.5

Sybase 10

Intersolv 2.12

Oracle 7.3

Oracle 7 v1.11 (16 bit)

Intersolv 2.11 (Oracle 7)

SQL Anywhere 5.0

Sybase SQL Anywhere 5.0

Access 2.0

Microsoft Access 2.0

Access 7.0

Microsoft Access 3.4

INFORMIX 7.1

Intersolv 2.11

What are the system requirements for running TESTBytes?
TESTBytes requires an Intel 486 or Pentium running Windows 3.x, Windows 95 or Windows NT, with a minimum of 16 MB of RAM and 10 MB of hard disk space.


ODBC ISSUES

TESTBytes doesn't recognize my data source.
Be sure that if you have the 32 bit version of TESTBytes that you have the 32 bit version ODBC driver installed. The same goes for the 16 bit version too.

How do I define ODBC data source?
You can find this step by step information in your Users Guide chapter 1 Getting Started with TESTBytes. Be sure that the datasource is properly defined in the ODBC Administrator.

How does TESTBytes connect to my Database?

Connecting to the various DBMSs comprise the largest category of questions to Logic Works Technical Support. TESTBytes connects to your database via ODBC standard drivers, and setting up a datasource through the ODBC Administrator.


RUNNING TESTBYTES

When I run the TESTBytes application I am getting an error "Unable to load ODBCAPI.DLL".
This happens when you install TESTBytes without having any ODBC drivers installed. The best resolution to this problem is to have the user install their ODBC drivers before trying to run TESTBytes.

How does TESTBytes connect to my Database?
Connecting to the various DBMSs comprise the largest category of questions to Logic Works Technical Support. TESTBytes connects to your database via ODBC standard drivers, and setting up a datasource through the ODBC Administrator.


REFERENTIAL INTEGRITY

Will TESTBytes maintain the Referential Integrity During Data Generation?
TESTBytes will generate data to all the tables in your database with full referential integrity. For keyed fields that are linked to other tables, random data is collected from the user defined link table's indexes to make sure your data is sound. You will need to use the TESTBytes interface at this time to set up RI, this however will read directly from the database in the next release.

Can TESTBytes generate a 'recursive' or ' fish hook' relations?
Not at this time, it is however going to be implemented in the next version.


DATA PROFILES

How can I create custom data profiles?

When you click the profile button, TESTBytes displays the Data Profiles dialog which allows you to create, modify, copy, and delete data profiles for all datatypes (CHAR, NUMBER and DATE).

Then click new to open the New Profile dialog for the selected datatype. TESTBytes displays a different dialog for defining a CHAR, NUMBER, or DATE Custom profile, but the process is the same.

Each time you create a custom data profile it is available from the Data Profiles list box to generate data.

Can I import profile data?

Yes, In TESTBytes, choose Import Profile Data from the Options menu. Locate the text (*.txt) file to be imported into the TESTBytes and click OK. The New Profile Name dialog is displayed. Complete the New Profile Name dialog with the name of the profile to be imported. The profile name must not match the name of any currently existing data profile. When finished, TESTBytes displays a confirmation dialog. Click OK again to complete the import process.


GENERATING FLAT FILES

Can I create flat file formats?
A really useful feature in TESTBytes is the ability to define custom flat file formats and then generate data to a flat file using that format. This allows you to test your databases with large amounts of data and also to generate data for external applications like mail-merge applications and ODBC non-compliant applications. You can generate data for any application that has the ability to read or import separated and delimited files, and fixed length records.

How do I create a flat file?
First click on the file def button. The flat file formats dialog is displayed. Click the New button to define a new file format. Complete the dialog with a format name. Click the OK button. Click the Add button to define a new field, TESTBytes displays the Define Field dialog. You can use the edit button to make changes to selected existing fields. You cannot change field names. To change a field name, you must delete the field and add it again with the new name. You can use the Delete button to delete selected existing fields. Complete the Define Field dialog. Click the OK button to save the new field definition. Repeat these steps to create each field. Click on the Save button to save the new flat file format.


UNABLE TO GENERATE DATA

Getting an error Unable to generate all rows requested...
If you are trying to generate data and get an error message "unable to generate all rows requested" this could be because there are constraints on the columns or table that conflict with the profiles you have specified, please verify Referential Integrity column constraints and unique indexes". This error pops up when you don't have your indexes defined.