Home  |   French  |   About  |   Search  | mvps.org  

What's New
Table Of Contents
Credits
Netiquette
10 Commandments 
Bugs
Tables
Queries
Forms
Reports
Modules
APIs
Strings
Date/Time
General
Downloads
Resources
Search
Feedback
mvps.org

In Memoriam

Terms of Use


VB Petition

Bugs: Jet 4.0 SP3: Text IISAM does not work without txt file extension

Author(s)
Dev Ashish
  If you have been using TransferText to import and export files that did not have any extension in their names, then installing Jet40SP3.exe (Updated version of Jet 4.0) will cause your code to stop working.

The information in this article is obtained from the following Knowledge Base articles

Article ID: 239471
Jet 4.0 Text IISAM Allows Users to Append Lines to System Files
Article ID: 239114
ACC2000: Updated Version of Microsoft Jet 4.0 Available in Download Center

After you install the updated version of Jet, you will only be able to use the Text IISAM to update text files with the following extensions:

  • txt
  • csv
  • tab
  • asc
  • htm
  • html

Installing Microsoft Data Access Components MDAC 2.1.2.4202.3 (GA) and the Microsoft Jet 4.0 SP3 update adds the following registry key when a program loads the Text IISAM.

HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\Engines\Text\DisabledExtensions

The Value data for the registry key is:

!txt,csv,tab,asc,htm,html 

NOTE: The first release of Jet 4.0 SP3 did not provide the use of an exclamation mark (!). When you place an exclamation mark at the beginning of the Value data, you can modify only files with the extensions listed. When you do not place an exclamation mark at the beginning of the Value data, you cannot modify files with the extension listed. With the Jet 4.0 Text IISAM, you cannot set the registry key to an empty string. Therefore, if you do not want to block access to any system text files, you should set the registry key to a binary file name extension. For example, you can use .exe.

To resolve the error, either rename the file extension to one of the enabled extension types or modify the DisabledExtensions registry key using the methods in this article.


© 1998-2010, Dev Ashish & Arvin Meyer, All rights reserved. Optimized for Microsoft Internet Explorer