Copyright: Copyright 1994, Baler Software Corporation


Visual Baler Messages

B

Backup failed

Baled application is running

Bin range incorrect

C

Cannot allocate required memory

Cannot find dialog in the database

Can't create file

Can't delete all

Can't execute HC31.EXE

Can't find BEGIN_MENUBAR

Can't find BEGIN_PULLDOWN

Can't find END_MENUBAR

Can't find END_PULLDOWN

Can't find required text

Can't hide all columns

Can't invoke system

Can't launch program

Context ID is required

Context label required

Criteria and Output ranges overlap

Critical file object error

D

Dialog database is damaged

Dialog is too large

Disk error

Disk full

Disk write-protected

Drive not ready

Duplicate Context ID

Duplicate field names

E

Error accessing Help database

Error adding dialog to database

Error closing file

Error creating file

Error deleting dialog from database

Error in margins

Error linking project information

Error modifying dialog in database

Error opening file

Error reading file

Error writing RTF file

Exe name field contains an invalid file name

F

File doesn't exist

Formula too complex

H

Help database is damaged

Help file name is invalid

Help files cannot be shared

Hidden columns/rows in title area

I

Information lost during saving

Input and Output ranges overlap

Internal error "error"

Invalid address

Invalid BWB file

Invalid directory

Invalid formula

Invalid Macro Argument

Invalid page number

Invalid Print Range

K

Keyword or range name not recognized

L

Last page must be greater than the first

M

Macro argument missing

Macro execution error

Macro not supported

Macro Syntax Error

Memory allocation failed

Memory template too large

N

Named setting already exists

Network is busy

No Help database topics

No input cells in range

No room to display a pane

No RTF file name specified

No Selection in display

No workbooks to Bale

O

Output dir field contains an invalid DOS path

P

Paper orientation not supported

Paper size not supported

Path specified is invalid

Printer driver version out of date

Protected cell

Protected Workbook

R

Read-only file

S

Secured cell

SHARE.EXE not installed, possible file damage

String too long

T

Too many open files

U

Unable to open file

Unexpected sharing violation


Bin range incorrect

You specified a 3-D range for Data|Distribution|Bin range.

Set a single-sheet, single-column bin range.


Backup Failed

File|Save As|Backup failed because the file's .BAK file is in use by another user, or a problem occurred with the file or disk.

Save the file with a different name or save to a different disk.


Can't create file

This error can result from the following conditions:

The disk is full. Save the file on another disk or in another directory.

The file you specified exists as a read-only or hidden file. Save the file on another disk or in another directory.

The directory does not  exist, or you did not specify a file name.  Enter a correct directory and file name.

The disk drive door is open. Close the disk drive door and try again.

You have an invalid character in a file name.  Enter a correct file name.


Memory allocation failed

There is not enough memory to perform this action.

Save the file, choose File|Exit to quit, then restart Visual Baler.

Close other running applications and all non-essential workbooks and try again.

Use Edit|Clear to completely delete un-needed cells from you workbooks


Duplicate field names

Your database table has duplicate field names.

Rename or remove the duplicate fields.


Can't hide all columns

A workbook must have at least one displayed column.


Can't invoke system

The  {SYSTEM} macro command, had one of the following problems:

Baler could not find COMMAND.COM.

Baler could not open COMMAND.COM. because you are using the maximum number of files your operating system allows.  Use File|Close on one or more of your active files, or close other application programs.

There is not enough memory to invoke the operating system.


Can't launch program

An error occurred trying to run an application specified in a {LAUNCH} command. This may be caused by:

There is not enough memory to start the application.  Remove unnecessary files from memory and try again.

The application does not exist or is not a Windows application. You can't launch DOS programs.

A file needed to run the application is missing or corrupted.  Re-install the application and try again.


Criteria and Output ranges overlap

You set overlapping criteria and output ranges using Data|Query.

Set criteria and output ranges that do not overlap.


Invalid directory

The following can cause this error:

You specified a directory that does not exist. Re-specify the directory name or path.

You entered an invalid character in a file name. DOS determines the characters allowed in a file name.


Drive not ready

You are reading or saving a file on to a disk drive whose door is open or that does not have a disk.

Correct the problem and try again.


Disk error

The disk may be damaged, or the drive head may be out of alignment.

Try another disk.

Check the alignment of the disk-drive head.

If trying to read the file, try using another computer.


Disk full

The disk does not have enough room for the file.

Save the file to another disk so you do not lose the file.


Disk write-protected

You can't save a file on a disk with a write-protect tab, or on a disk manufactured without a write-protect notch.

Remove the tab or replace the disk with one that is not write-protected.


Error reading file

Check that the file is a valid Visual Baler file type.

Use the Windows File Manager to check the size of the file on disk to ensure that you are not trying to read an empty file (file size shows 0 bytes).

The file may be corrupted.  Visual Baler may be able to read part of the file.


File doesn't exist

The file does not exist in the directory you specified.

Repeat the command and enter a correct path and file name.


Read-only file

You tried to save to an existing read-only file.

Choose File|Save As to save the file under a different file name.

Use the File Manager to remove the read-only attribute from the file. (Use File|Properties).


Formula too complex

The formula is too long or too complicated.

Break the formula into one or more smaller formulas.


Information lost during saving

When saving workbooks to files with .WK1 or .WK3 file extensions you lose some Visual Baler features those file formats don't support.

To avoid losing data, choose File|Save As and save the file as a .BWB file.


Incorrect password

Either:

You entered an incorrect password when reading a password-protected file using File|Open.

You entered the wrong password when you open the Project Security Settings dialog

Re-enter the password.  Visual Baler passwords are case-sensitive, so use the exact combination of uppercase and lowercase letters used to create the password.


Input and Output ranges overlap

Input and output ranges for Data|Query operations must not overlap.

Set the input and output ranges so that they do not overlap.


Internal error "error"

Visual Baler uses this message to report unexpected conditions during execution.

Record the error message and contact Baler technical support.

How to contact technical support


Invalid address

The following can cause this error:

The address does not exist, such as ZZ1 or A1..A9000;

The range address is syntactically incorrect, such as A:A1..B:A:1.

The range name does not exist.  Use Range|Name to select a valid range name, or create a valid range name for the address.

A cell specified as the location argument for a {DISPATCH} macro command contained an entry that did not evaluate to a valid location.

A required range text box was left empty. Repeat the command and specify a range in the range text box.


Macro argument missing

One of the following problems occurred while running a macro:

One of the required arguments is missing.

A {DEFINE} command has fewer arguments than the subroutine that called it.  {DEFINE} commands must have the same number of arguments as the corresponding {subroutine} call.

See Also

Macros


Macro not supported

The macro command is not supported by Visual Baler. It may be a menu keystroke sequence or advanced macro command supported by Baler for DOS. Please see User's Guide - What's new for Baler for DOS users, for equivalent macro commands and work-arounds.

See Also

Macros


Protected cell

Page Settings|Protection|Enable is on and:

You tried to enter, edit, copy, or move data into a protected cell or range.

You used a command that moves columns or rows, such as Range|Delete, Range| Insert.

Select Page Settings|Protection|Disable to unprotect the page.

See Also

Page Settings


Secured cell

Project Settings cell security is on for the type of cell and:

You tried to enter, edit, copy, or move data into a cell or range of that type.

You used a command that moves columns or rows, such as Range|Delete or Range|Insert.

Use Project Settings for the mode you're using to unprotect the cell type you want to change.

Set Project Security to "Open".

See Also

Project Settings


Too many open files

You have too many files open.

Use File|Close to remove files from memory.

Increase the number of file handles specifies in your CONFIG.SYS file.


Hidden columns in title area
Hidden columns/rows in title area

You can't set titles (Window|Titles) with hidden columns to the left of the cell pointer or hidden rows above the cell pointer.


Can't delete all

You've selected all remaining columns, rows, or pages and used the Range|Delete command. The workbook must have at least on column, one row, and one page.


Invalid Macro Argument

One or more of the arguments in a macro command are not valid.

Check that the type is correct (you don't have a value where a string is required.

See Also

Macros

Macro Arguments


Macro Syntax Error

A macro statement has a syntax error such as:

Not enough or too many arguments.

You may be missing an argument separator (usually a comma).

You may have a space between arguments.

See Also

Macros

Macro Arguments


No Selection in display

You are setting Worksheet Titles but the cell pointer is too many columns to the right or too many rows below cell A1. This would result in no area on the screen that is still scrollable.

You must move the cell pointer closer to cell A1.


Invalid Formula

You've entered a formula that has an error in its construction. For example:

+A1++A1

@sum(2)


Unable to open file

You tried to open a file that Visual Baler cannot read.

Check that the file is a valid Visual Baler file type.

Use the Windows File Manager to check the size of the file on disk to ensure that you are not trying to read an empty file (file size shows 0 bytes).

The file may be corrupted.  Visual Baler may be able to read part of the file.


Protected Workbook

The workbook you tried to open has a different lock number than the one currently in effect.

Change the lock number: Tools|Project|Security


No Input Cells in Range

The following macro commands set up a restricted range that allows user input in Input Cells only. The range you specified has no Input Cells.

{RANGE-INPUT}

{RESTRICT}

{DRILLRESTRICTON}

{DRILLRESTRICTRI}


Macro Keyword not Recognized

Visual Baler does not recognize the the string in braces as a valid macro keyword. You may have misspelled a valid keyword, or be using a macro that Baler does no support.

See Also

Macros


Invalid Print Range

You specified a print range that is not in the active workbook.

Specify a range in the active workbook, switch to the workbook or choose File|Open to open the file containing the range you want to print.


Invalid Page Number

The page number in (File|Print|From page or To page) is larger than the actual number of pages in the print range.


Last page must be greater

You set a last page number (File|Print|To page) the is less than the starting page number.


Named setting exists

The name you entered for your print settings already exists.

Enter a unique name.


Error in Margins

The following can cause this error:

Your combined left and right margin settings are greater than the width of the paper.

Your combined top and bottom margin settings are greater than the length of the paper.

Margins, header and footer equal or exceed page length, leaving no space on the page for the print range.


Paper size not supported

The printer you've selected (File|Printer Setup) does not support the paper size you selected.


Paper orientation not supported

The printer you've selected (File|Printer Setup) does not support Landscape printing.


Printer driver out of date

Your current Windows printer driver does not support the Printer Setup dialog box.


Context label required

Each help topic must have a unique Context Label.


Error Opening File

Could not open the specified Help source file.

Check that the file you selected was is a valid Visual Baler Help source file (.BHP).


Error closing file

A file error occurred when closing the Help source file.

Check that the .BHP file still exists.

Check that other users on a network are not using the file (and that you and they have SHARE.EXE installed correctly.)


Error creating file

Could not create a new Help source file.

You tried to save too many files on a disk. Save to another disk or another directory.

The file you specified was hidden on disk. Save to another disk or another directory.

You specified a directory that did not exist, or you did not specify a file name. Check the directory and file name.

You entered an invalid character in a file name. DOS determines the characters allowed in a file name.


Help file cannot be shared

The Help source file you selected is in use on a network drive or by some other application running on your local drive.

Wait until the other application closes the file or choose another file.

To share help database files on a network:

Install SHARE.EXE

Set the following line in your BALER.INI file:

ShareHelpDB=TRUE


Context ID is required

Each help topic must have a unique Context ID number. You use the Context ID number to refer to help topics in your macro code.


String too long

You've entered too many characters in the cell.  Visual Baler supports a maximum of 256 characters.


No room to display a pane

You're using Windows|Split to create two windows, but the cell pointer is in a cell too close to an edge of the current window. Baler uses the cell pointer position to determine the size of each pane.

Move the cell pointer to the center of the window, or use the Window Split control at the lower right of the workbook window to create split windows.


Can't find BEGIN_MENUBAR

Your {DisplayMenuBar} command uses a Menu Table that does not have the BEGIN_MENUBAR keyword in the correct cell.


Can't find BEGIN_PULLDOWN

Your Menu Table has a PULLDOWNITEM keyword without a corresponding BEGIN_PULLDOWN keyword.


Can't find END_MENUBAR

Your Menu Table is missing the final END_MENUBAR keyword.


Can't find END_PULLDOWN

Your Menu Table has a Pull-down block started with a BEGIN_PULLDOWN keyword, but without a matching END_PULLDOWN keyword.


Can't find required text

Your Menu Table has a MENUITEM or a PULLDOWNITEM without any display text.


Memory template too large!

Your Menu Table is too large. The main menu resource it defines is too large to fit in memory.

Close other Windows applications or un-needed workbooks to free memory space.


Macro execution error

Use single-step mode to find which macro command caused this error. Several conditions can cause this error:

1	The macro parser has found an invalid argument.

Check for spelling errors, such as a misspelled page name or range name.

Check the cell type for each argument. For example if the macro expects a range name, cell address or a pointer to a cell that has a value, you may have a reference to a cell that has a label.

2	The macro operation could not complete successfully because of som un-determined internal error.

Check that your security settings (are you in Bind or Close mode?) aren't preventing changes to cells referred to by your macro.

Check the syntax for the macro command in on-line help or the @Functions and Macros book.

Try the same macro command in a separate workbook by itself to see if it works there.

See Also

Macros


Help database is damaged

An undetermined file operation has changed the help database file. Visual Baler cannot read the file. This can happen if you turn off your PC or re-boot while Visual Baler is running.

Delete the damaged help (.BHP) database file.


Duplicate Context ID

You've entered a context ID number that already exists in the help database.

Enter a different number.


Network is busy

You're sharing the help or dialog database on a network and the network has responded to a file request with a "busy" return code.

Please wait a moment and try again.

If this condition persists, contact your network administrator.


Share.exe is not installed, possible file damage.

When using the Help or Dialog database on a network, SHARE.EXE must be installed and loaded on your local PC. SHARE.EXE  prevents simultaneous access to the same records, which could result in damage to the database.

Refer to your DOS manual for information on SHARE.EXE.

If you do not have the database on a network drive or do not intend to share its use, you can avoid this message by changing a line in your VBALER.INI file: Change:

ShareHelpDB=TRUE

TO

ShareHelpDB=FALSE


No Help database topics

You've selected Tools|Custom Help|Help Compiler, but there are no help topics created yet.

Open an existing help database, or start a new one and enter help topics before compiling.


No RTF file name specified

You must enter a filename for the output file before you can compile your help.


Error writing RTF file

Some disk error prevented writing to the specified output file.

The following can cause this error:

You added an extension to the help file name. Do not include the .HLP extension.

You tried to save too many files on a disk. Check free disk space.  Save to another disk or another directory.

You tried to save to a read-only disk or network directory. Save to another disk or directory.

The file you specified was hidden on disk. Save to another disk or another directory.

You specified a directory that did not exist, or you did not specify a file name. Check the directory and file name.

You entered an invalid character in a file name. DOS determines the characters allowed in a file name.


Can't execute HC31.EXE

In trying to compile your help file, Baler could not find HC31.EXE. This is the Microsoft help compiler program. It must be in your current directory, or in a directory that is included in your PATH environment variable.


Error accessing Help database

An undetermined help database error occurred.

Check that the .BHP file still exists.

Exit Visual Baler, exit Windows and restart. Call technical support to report the steps leading up to the error.


Critical file object error!

Visual Baler detected an internal error during a file operation.

Exit Visual Baler, exit Windows and restart. Call technical support to report the steps leading up to the error.


Unexpected sharing violation

You're sharing the help or dialog database on a network and SHARE has responded to a file request with an "Unexpected Error" return.

Check that you have SHARE.EXE installed properly (check your DOS manual).


Dialog database is damaged!

An undetermined file operation has changed the dialog database file. Visual Baler cannot read the file. This can happen if you turn off your PC or re-boot while Visual Baler is running.

Delete the damaged dialog database file.


Dialog is too large

Visual Baler cannot allocate enought memory to support this dialog.

The dialog box you're designing has too many components. Consider splitting it into two or more separate dialog boxes.


Error adding dialog to database

An error occurred while updating the dialog database. The dialog was not saved properly.

Exit Visual Baler and call technical support to report the steps leading up to the error.


Error modifying dialog in database

An error occurred while changing a record in the dialog database.

Exit Visual Baler and call technical support to report the steps leading up to the error.


Error deleting dialog from database

An error occurred while deleting a record from the dialog database. This is due to an internal error in the database.

Exit Visual Baler and call technical support to report the steps leading up to the error.


Cannot find dialog in database

The dialog name (Object ID) you specified in {CREATEDIALOG} is not in the dialog database.

Check the dialog name name you used.

Check that the dialog database file (.BDG) is in the same directory with your application files.


Cannot allocate required memory!

The current operation was unable to allocate the memory it required.

Close other running applications and all non-essential workbooks and try again.

Use Edit|Clear to completely delete un-needed cells from you workbooks


Invalid BWB file

One or more of the workbook files you specified to Bale, is not a valid .BWB file.

Check that you have the file names correct on the Bale dialog.

Check that you can open the specified .BWB files.


Error linking project information

Bale could not add resource information to your run-time .EXE file.

Check that your file name for your .EXE is a valid DOS file name.

Check that your output directory is valid.


Baled application is running

You've tried to Bale your application, but a previous version is already running and so, the .EXE files is "in use".

Exit the run-time application before Baling a new one.


No workbooks to Bale

You must have at least one workbook specified in the workbook list on the Bale dialog. Or you must have at least one workbook open at the time you Bale.

Check the list of workbooks on the Bale dialog.

See Also

Bale - Workbooks


Help file name is invalid

The file name you used for your help file is invalid.

Check the number of characters in the file name (8 is maximum).

Check for invalid characters: DOS allows: A-Z, 0-9, and these symbols:  _ ^ $ ~ ! # % & - { } ( ) ' ` , all other special characters and symbols are invalid.


Path specified is invalid

In the Bale dialog, the path you entered is not a valid path.

Check that the directories you entered actually exist.

Check that you entered them correctly without spelling mistakes.

Baler cannot use directories with file extensions, such as: OUTPUT.001


Exe name field contains an invalid file name

The name for your .EXE file in the Bale dialog is not a valid DOS file name.

Check the number of characters in the file name (8 is maximum).

Check for invalid characters: DOS allows: A-Z, 0-9, and these symbols:  _ ^ $ ~ ! # % & - { } ( ) ' ` , all other special characters and symbols are invalid.


Output dir field contains an invalid DOS path

In the Bale dialog, the path you entered for the output directory is not a valid path.

Check that the directories you entered actually exist.

Check that you entered them correctly without spelling mistakes.

Baler cannot use directories with file extensions, such as: OUTPUT.001


The trial version does not save WKx files

You cannot use the File|Save As command to save to file formats other than .BWB (Baler Workbook) in the trial version.

The full commercial version of Visual Baler reads and writes .WK1/.FMT and .WK3/.FM3 files.


The Help compiler is not available in the trial version

You cannot compile your custom help in the trial version. This operation requires Microsoft's help compiler.

The full commercial version of Visual Baler includes the help compiler along with Microsoft's HotSpot editor that lets you add graphics with hot links to topics in your help files.


Not available in the trial version

This feature is not supported in the Visual Baler trial version.

The full commercial version of Visual Baler does support this feature.