On May 18, 11:34=A0am, Wayne <cqdigi...@[EMAIL PROTECTED]
> wrote:
> On May 19, 12:01=A0am, lyle fairfield <lyle.fairfi...@[EMAIL PROTECTED]
> wrote:
>
>
>
> > I don't know. A Search for "can't create the output file" in this
> > newsgroup doesn't find anything pertinent; ditto for 2285.
>
> > But a general Google search for "can't create the output file 2285"
> > returns many hits. A really quick glance at these might make one
> > wonder if the error is related to file attributes or folder
> > permissions. But when you "LoadFromText" you're not creating an
> > "output file", at least not ostensibly (VB/Access might be doing this
> > with a tem****ary file behind the scenes.)
>
> > So, where from here? Have you tried "On Error Resume Next" to see if
> > any forms load?
>
> > You're writing, obviously, to the folder where the (new) app lives.
> > And you must have write permissions there or SaveAsText would fail.
>
> > That's all that comes to mind on a Sunday morning, but several other
> > people are using the SaveAsText-LoadFromText duality as a cleanser and
> > perhaps someone will recognize the problem and be able to help.
>
> Thanks for your help Lyle. =A0I tried using "On Error Resume Next" and
> the result was interesting. =A0An "Errors.txt" file was created for each
> form, 37 of them in this case. =A0Each Errors.txt file contains
> nothing. =A0I thought that Vista might be doing strange things to me and
> booted into XP but the result was the same. =A0As you say, perhaps
> someone else will be able to help.
A little further search brings up this error described but no
suggestion as to its cause or cure. If you were to post the text file
for the first form that fails, some of us might see if we can load the
form into a database with the LoadFromText method. If so, we will know
its not your form. If not, we might be able to study the problem in
general terms, (or you could just send me the text file and I'll post
it: lyle dot fairfield at gmail dot com).
|
