Error Creating Form

I have just had to re-install windows and delphi after my system files became corrupted and now one of my forms in my delphi 2.01
project will not open.

I get the message cannot open form - unspecified error

I have reinstalled all the components for the form but I still cannot load it up. When the program runns it works ok until I get an interaction between the ChartFX and a VCFormula 1 table at which point I get an  Exception - EAccessViolation

Anybody have a solution?
essbbAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

StevenBCommented:
 Beware the Formula1 component, all is not as it seems. This component forms the backbone of our project, a decision we made some time ago, but are now starting to regret. The component behaves in a strange manner when run through Delphi. The most significant problem being that it generates access violations when its maximum values are exceded. (The maximum value is about 9.9e301 as I recall, it's in the help file under specifications). It does much the same when a single value greater than about 1e19 is entered into a formula.
  This is not the behaviour which I expected from a component that I'd payed a significant amount of money for, so I contacted the manufacturers. They told me that, in essence, their component did not specifically support Delphi (The decision to ship the trial version with D2 and 3 was made by Borland, who own the rights to the trial version) They said that the component works perfectly under VisualBasic (I checked, it seems to) and that it fullfilled all the criteria specified by Microsoft for the ActiveX specifications. They put the blame with Borland and suggested that the Delphi support for ActiveX controls was not quite 100%. (There was some explanation given here involving Windows DLLs and changing Microsoft standards, but it got a bit beyond my knowledge of the underlying windows structure). I phoned Borland and put these accusations to them. They were less than direct in their answers, refusing to confess guilt directly, however they did hint that the fault might be theirs. There was also some vague suggestion that an upgrade for D3 in early August might resolve some of these problems.
  That is the story so far as far as I can ascertain. The question of where it leaves you still remains. From what you've described it sound to me like you are exceding the maximum values in the F1Book and causing the Access violation. Check if this is the case, and if so try and put in some error trapping to prevent it happening. I know this is very difficult and we havn't managed to implement it in our project. If this is not what is occuring then feel free to reject the answer, but please heed my warning and tread very carefully with Formula1. It can cause huge problems if you let it.

  Steven.

  P.S. If you discover any more Bugs etc. with F1 and Delphi then I'd be most grateful if you could let me know. You're the only other person I've found who uses the component.

  stemail@dial.pipex.com
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
essbbAuthor Commented:
Steven,

Our project only uses Formula 1 in a small way the table size is about 6 x 20 cells and the values rarely exceed 100. The point at which the program crashes is when I set the chartfx.maxserie to formula1.maxcol.

My Main Problem is that I Cannot display the form in design mode, this is when I get the error.
0
essbbAuthor Commented:
If you delete all refernces to the table (from both the .pas & .dfm) and then add a new one it works!
0
StevenBCommented:
F1UPDATE F1UPDATE F1UPDATE F1UPDATE F1UPDATE F1UPDATE F1UPDATE

  Recently discovered bug (Fortunately with very easy work around)

  Never do this : EntryRC := '';

  The empty string siezes the machine. Always check for empty strings.

  Steven.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Delphi

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.