Mising tablename property

This is a curiosity question rathe than a mission critical one. Intermittently when I save some units I get this message, generally a second save or a build all makes the message go away until the next time. The forms in question have a TTable dropped on the form but I assign the tablename and databasename programmatically. Surely this is reasonable and shouldn't lead to this message?

Thanks.

Tom.
boardtcAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

ronit051397Commented:
Can you show the code example?
0
boardtcAuthor Commented:
There is no code example. It happens with a number of units, occasionally a save or a compile gives "Missing Tablename property".
0
ZonnaldCommented:
Tom,
The most obvious time this message would apear is when you try to open the table in your code during run time.  Is this happening?  If it is, can you be sure that the event that sets the tablename occurs before the event that opens that table?

I would suggest that each time you open a table you check the tablename is not empty, if it is then go ahead and set it.
Also it is a good idea to check the Table.State property when doing post and make sure that it is in a dsEditModes state.

These things will help unwanted messages appearing, which confuse the end user.

Good luck

Zonnald

0
Fundamentals of JavaScript

Learn the fundamentals of the popular programming language JavaScript so that you can explore the realm of web development.

boardtcAuthor Commented:
Thanks for the comments. Prior to opening a table I always check the tablename property. However, this is not a run-time problem, like I say a second save/Build all always corretcd the problem until next time. This is why I'm not too worried about it, it only happens (at least once a day) at design time. But I still would like to know why. Thanks. Tom.

0
WilfredCommented:
I think you will get this message when table related property's are set (like indexname or if you have created some fields).
When you save your project Delphi tries to validate all  property's and cannot validate any of these table related property's.
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
boardtcAuthor Commented:
Ok, I'll see if I can track anyting down.

Tom.
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.