Oh, these lovely error messages ...

Yesterday I lost some 1,5 hours of my time in solving an issue with =
TranserTxt.

I am (in fact my users are) using the same app in both Access 97 and =
Access 2k
The app has code like DoCmd.TransferText acExportFixed, "DBSRel", =
"TabExportDBSDeb", "C:\Temp\Deb.fil"

This works in Access 97 (latest sp)
This bombs in Access 2k (also Access2003) with the error:
"Cannot update, database or object is read-only".


So I have been testing read-only issues or other restrictions on this =
db.
Also tested restrictions on the path used and so on..
I could not find anything wrong... Took me some time indeed... ^%&^&^&

At last I did find out that this issue is *solely* due to the file =
extension.
Note: I *must* use this extension 'fil' in order for this file to be =
read by another application.
When I use an extension like 'txt' or 'csv' there is no problem.

So I went on Googling ... (should have started with that !)
It appeared to be a known issue, called improved safety...
Look at Kb Q245407 http://support.microsoft.com/kb/245407

For Jet 3.5 only some 'system' extensions like =
bat,cmd,ini,sys,inf,vbs,js are restricted.
For Jet 4.0 all extensions *other than* txt,csv,tab,asc,tmp,htm,html are =
restricted.

Since I am only writing a *new* file from my table this security-measure =
seems to be overkill to me.
I might be wrong on this, but the *most* annoying is this totally wrong =
(to me) error message.

-- Would another error message like 'File-extension restricted' be more =
appropriate ??
-- Would this be difficult to implement ??
It would save me (and others) lots of time sometimes...

OT:
Another 'nice' error message yesterday on my machine (origin Mailwasher) =
was:

=20
An internal error has occured: Cryptic error message J877.2 non fatal

(Note: You have not done anything wrong)


I did not loose any time on that one since the program kept functioning =
;-)
=20
Arno R

Re: Oh, these lovely error messages ...

On Oct 31, 7:28 am, "Arno R" wrote:
> Yesterday I lost some 1,5 hours of my time in solving an issue with TranserTxt.
>
> I am (in fact my users are) using the same app in both Access 97 and Access 2k
> The app has code like DoCmd.TransferText acExportFixed, "DBSRel", "TabExportDBSDeb", "C:\Temp\Deb.fil"
>
> This works in Access 97 (latest sp)
> This bombs in Access 2k (also Access2003) with the error:
> "Cannot update, database or object is read-only".
>
> So I have been testing read-only issues or other restrictions on this db.
> Also tested restrictions on the path used and so on..
> I could not find anything wrong... Took me some time indeed... ^%&^&^&
>
> At last I did find out that this issue is *solely* due to the file extension.
> Note: I *must* use this extension 'fil' in order for this file to be read by another application.
> When I use an extension like 'txt' or 'csv' there is no problem.
>
> So I went on Googling ... (should have started with that !)
> It appeared to be a known issue, called improved safety...
> Look at Kb Q245407http://support.microsoft.com/kb/245407
>
> For Jet 3.5 only some 'system' extensions like bat,cmd,ini,sys,inf,vbs,js are restricted.
> For Jet 4.0 all extensions *other than* txt,csv,tab,asc,tmp,htm,html are restricted.
>
> Since I am only writing a *new* file from my table this security-measure seems to be overkill to me.
> I might be wrong on this, but the *most* annoying is this totally wrong (to me) error message.
>
> -- Would another error message like 'File-extension restricted' be more appropriate ??
> -- Would this be difficult to implement ??
> It would save me (and others) lots of time sometimes...
>
> OT:
> Another 'nice' error message yesterday on my machine (origin Mailwasher) was:
>
>
> An internal error has occured: Cryptic error message J877.2 non fatal
>
> (Note: You have not done anything wrong)
>
>
> I did not loose any time on that one since the program kept functioning ;-)
>
> Arno R

The same thing happened to me. It seems our lot in life to spend
hours finding ways to get around the mistakes of others... BTW,
renaming the file works.