Error: input past end of file in ...\Product.frx

12 May 2005 5:48 PM

Alan Silver

Hello,

I was just running an application in the IDE when it popped up with this
error. The line on which it stopped was fairly simple, just setting the
caption of a form. I had this the other day and found out that the frx
file was corrupt.

I tried deleting the frx file, but that gave loads of problems as some
of the info for the ComponentOne elastic controls on the form seem to be
stored in there, and without the frx file, the form was unusable.

As it happens, this file hasn't changed for a few days, so I was able to
restore a copy from backup, but what if I had changed it? Anyone know
why this error occurs and if there is anything that can be done about
it?

TIA

--
Alan Silver
(anything added below this line is nothing to do with me)

12 May 2005 8:11 PM

Ken Halter

"Alan Silver" <alan-silver@nospam.thanx> wrote in message
news:t3iA4zNKc5gCFwlY@nospamthankyou.spam...
> Hello,
>
>
> I tried deleting the frx file, but that gave loads of problems as some of
> the info for the ComponentOne elastic controls on the form seem to be
> stored in there, and without the frx file, the form was unusable.
>

There aren't many mentions of that error on Google and none in the MSKB.

This post, same problem, seems that it was caused by some property settings
that ended up corrupting the richtextbox control.

WYSIWYG printing from RichTextBox
http://groups.google.co.uk/group/microsoft.public.vb.general.discussion/browse_frm/thread/c1c8f31815fe1e27/bfafb65535d56524?q=%22input+past+end+of+file%22+(frx)+-dotnet+group:*.vb.*&rnum=5&hl=en#bfafb65535d56524

Sounds to me like the only way to "fix it for good" is to set the properties
for that control at runtime instead of at design time. There's probably some
special sequence of characters there that are fooling VB into thinking that
its not done loading the frx file.

If you can reproduce the problem at will, you may want to report the
findings to ComponentOne.

--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
DLL Hell problems? Try ComGuard - http://www.vbsight.com/ComGuard.htm
Sign up now to help keep VB support alive - http://classicvb.org/petition
Please keep all discussions in the groups..

16 May 2005 9:37 AM

Alan Silver

>> I tried deleting the frx file, but that gave loads of problems as some of
>> the info for the ComponentOne elastic controls on the form seem to be
>> stored in there, and without the frx file, the form was unusable.
>>
>
>There aren't many mentions of that error on Google and none in the MSKB.

Yeah, I noticed that ;-(

>This post, same problem, seems that it was caused by some property settings
>that ended up corrupting the richtextbox control.

I saw that (and a few similar ones about the RTB), which is what made me
suspect the ComponentOne control. The suspicion was supported by error
messages about various properties of that control.

>Sounds to me like the only way to "fix it for good" is to set the properties
>for that control at runtime instead of at design time. There's probably some
>special sequence of characters there that are fooling VB into thinking that
>its not done loading the frx file.

Trouble is that I don't know what properties are being set by the
control. The control is their sizer, which is hard enough to work with
at design time, at run time it would be impossible.

Given that I don't have much on the form that would alter the frx file
(afaik), I have taken a copy of it and just restore when the problem
occurs. This is fine as long as the frx file doesn't change, but it
isn't really a solution.

>If you can reproduce the problem at will, you may want to report the
>findings to ComponentOne.

Ever tried their technical support? Occasionally they manage to answer a
question in a reasonable time, often they can't answer it, sometimes it
takes them a very long time indeed. I just closed an issue with them
that took over seven months (!!) to answer, producing just five lines of
code in the end. I don't have a great deal of confidence in their
support.

If it were a practical option, I would pull out the control altogether
as it's more trouble than it's worth. I have had other (unresolved)
issues with it as well. Trouble is, it would take so long to redo the UI
without this control that I can't justify it.

Thanks for the reply.

--
Alan Silver
(anything added below this line is nothing to do with me)