Errors

hello people :)

As i close my application a message appears; "Invalid Property Settings - Programming Error". What exactly does this mean?

What are the possible causes of an I/O Error 123?
I/O error 123 returns the message "The filename, directory name or volume label syntax is incorrect".
dabestprogrammerindauniverseAsked:
Who is Participating?
 
MadshiConnect With a Mentor Commented:
You might want to try my package "madExcept", which can catch exceptions at runtime (outside of the IDE) and then tell you where in your sources it happended. It is free for non-commercial usage (only). See here:

http://help.madshi.net/Data/madExcept.htm

However, in your specific situation my package can only help if the io error is raised as an exception. If someone only shows a message box without raising an exception, it's not caught by madExcept.

Regards, Madshi.
0
 
MadshiCommented:
Shouldn't "dabestprogrammerindauniverse" know the answer to those questions?   :-)   Just joking...

Please run your application inside of Delphi's IDE. Then Delphi should show you the source code line which is guilty for producing the 2 errors you mentioned. Then please show us the code around those lines. Then we can surely help.

I never saw the first error yet. The second error can occur in several situations, e.g. if file functions are called with an incorrect path.

Regards, Madshi.
0
 
Hamlet081299Commented:
"Invalid Property Settings - Programming Error" doesn;t look like a Delphi error.

I suspect this may be coming from some 3rd party component you are using.  What 3rd party components are you using.
0
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

 
Hamlet081299Commented:
Or I guess it could be that this is some code you've inherited.  

In Delphi try doing a "Find in files" for "Invalid Property Settings" and select the "Search all files in project" option.  With luck this may turn up your problem.
0
 
dabestprogrammerindauniverseAuthor Commented:
Shouldn't "dabestprogrammerindauniverse" know the answer to those questions?   :-)   Just joking...

<--hahaha...i'm supposed to be the best after i'm done asking all my questions :) just kidding

actually, the io error 123 isn't very easy to catch in my program...it happens very seldom and usually it doesn't happen when i run my code in delphi that's y i wanna know the causes so i can search for it in my code :)

thanks madshi and hamlet!
0
 
dabestprogrammerindauniverseAuthor Commented:
hamlet...
you're right, the "Invalid Property Settings - Programming Error" is an error by XceedZip, a third party component that i use...thanks!
:)
0
 
Hamlet081299Commented:
Which happens first the io error 123 or the "Invalid property settings"?

This is important, because often only the first error really matters (although additional errors usually indicate poor error recovery).
0
 
dabestprogrammerindauniverseAuthor Commented:
Actually, they happen independently. The I/O error happends during a different instance.  Thanks! :)
0
 
dabestprogrammerindauniverseAuthor Commented:
thanks madshi...what do you exactly mean by:

"However, in your specific situation my package can only help if the io error is raised as an exception. If someone only shows a message box without raising an exception, it's not caught by madExcept."

thanks again...i'll try out your package and see how it helps

0
 
dabestprogrammerindauniverseAuthor Commented:
thanks madshi...what do you exactly mean by:

"However, in your specific situation my package can only help if the io error is raised as an exception. If someone only shows a message box without raising an exception, it's not caught by madExcept."

thanks again...i'll try out your package and see how it helps

0
 
MadshiCommented:
I mean, madExcept detects *exceptions*, nothing else. If you do this:

raise Exception.Create('test');

Or if you do this:

PInt(0)^ := 0;  // access violation

Or anything like that, then madExcept will catch it. But if you do this:

if CreateFile(...) = INVALID_HANDLE_VALUE then
  MessageBox(0, 'Error in CreateFile', 'error', MB_ICONERROR);

Or something similar, then madExcept will NOT catch it. Why should it? For madExcept it looks like a plain message box. No reason to catch it.
0
 
dabestprogrammerindauniverseAuthor Commented:
got it...will try it and points are on the way!
thanks!
0
 
MadshiCommented:
Please give me the points only if my stuff helps you.
0
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.

All Courses

From novice to tech pro — start learning today.