Icon View Incident Report

Serious Serious
Reported By: Bill Miller
Reported On: 10/25/2000
For: Version 2.03 Build 1
# 642 Exists Function in TDBISAMTable Component Returns Invalid Results Under Windows 95/98

I noticed a strange occurance with the 'EXISTS' function in version 2.03. It appears that the Windows API call, WNetGetUniversalName, does not consistently return the correct UNC Path. And, DBIsamTable.Exists, depends on this function to work. Any table I use this function on keeps getting overwritten because the exist fails so I create a new ones.

I wrote a simple program that takes an input path, calls the api function, and returns the UNC. Here are my results from running this program on different version of Windows:

Windows 2000: Perfect.
Windows 98: Returns only the drive as UNC. The rest of the path is discarded.
Windows 98 SE: Returns only the drive as UNC. The rest of the path is discarded.
Windows 95: Returns an empty string or a garbage string.
Windows NT 4.0: Perfect


Resolution Resolution
Fixed Problem on 10/26/2000 in version 2.05 build 1
Image