Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Why does the SilkTest error "Numeric field overflow" occur in DB_FetchNext when testing Excel?

Why does the SilkTest error "Numeric field overflow" occur in DB_FetchNext when testing Excel?

This error is due to Excel rather than SilkTest. The cause is that Excel considers the format of each cell from its second row. If the first item of the second row is a number, it considers that the rest should be numbers.

There is no problem with this in Excel but once another application interacts with Excel to query the cell value, the problem arises. If say the third row is not a number, you will get the error message Numeric field overflow.

This issue can be overcome by modifying all the cells to place a single quote in front of every cell value.

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 19:26
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.