Nathan Wild

Remy: Thanks very much! With your code, I can see all top level windows flicker a little when the broadcast call is issued, but my shell still does not recognize the new variable even after the process terminates. Closing and opening a new shell does work, but this is not what I'm after... Starting to thing that this is not possible with Windows?!

This is correct... If I run my process to set the variable, then spawn a new shell it works... So it seems like it's just the broadcasting part of this process that doesn't work?

Stéphane Wierzbicki: That post was helpful, but seems to be pretty much what I am doing? I changed my code to use SendMessageTimeOut(), which seems to make all the top level windows that I have open flash a little, but seems to leave my live environment otherwise untouched 😞 Dave Nottage: That too was very helpful, although all it really told me is that I am fighting a losing battle 😉

Can you post a sample project that exhibits this behaviour?

In the RadStudio design-time object inspector some properties of some components show up highlighted, for example LiveBindings, CustomHint, PopupMenu, etc. Is there a way to define which properties show up highlighted? I don't much care about LiveBindings or CustomHint's, but I would REALLY like things like Name and Caption that I use ALL THE TIME to be easier to find in the list. I couldn't find anywhere in the OI configuration to change this. Any guidance much appreciated 🙂

I am using a DBNavigator control in one of my applications and for some reason, When I place it on the form it looks fine, but as soon as I connect a datasource to it, all the buttons lose their colour. NOTE: I don't mean they are greyed-out / inactive. I mean where they used to show blue glyphs for the first, previous, next and last buttons, they now show grey ones. They work normally, and grey-out as they should depending on the state of the underlying dataset, but the difference between an enabled button and a disabled on is very hard to see without the colour! See the attached screen shot. The control on the right was just dropped onto the form, but does not have its datasource property populated. The one on the left is identical, except that it is connected to a TDataSource. This is definitely the result of a VCL theme thing, but I can't find any properties that allow me to tell this control to ignore the theme (i.e. the standard "StyleElements" property) Any guidance appreciated!

Good grief... It never even occurred to me to check and see if TDBNavigator had a StyleElement property... It is missing from the design-time inspector, so I just assumed it did not... Setting DBNavigator.StyleElements := [seFont,seBorder] had the desired effect. Thanks!

What do you mean by "returning"?

Sorry... I am using Pervasive.

I am working with a table that has a large number of fields which are ALL set up as NOT NULL. 90% of these are unused, but need to be populated when inserting new records. Is there an easy / automatic was to tell FD to automatically populate '' and 0 values as appropriate for data type when inserting new records?

Oh yes, of course... I was just hoping that there was a way to do this somewhat more automatically...

Lovely... but where does that leave those of us who only have 10.1? 😞

So what is the best approach to do this? My end result is that I want to allow the end user to input a key value and then pass that to a a query as a parameter. This works perfectly the first time, but when I close the query, set a new parameter value and then re-open the query, I get this "SQLBindParameter has not been called for Parameter #2" error. Sure;y clearing and re-setting the entire SQL statement is not required?

Is there an easy way to see EXACTLY what query FireDAC is passing through to my database server? After it does all the parameter substitutions, and automatic jiggerey pokery? I've had a few weird errors and I think being able to see this would be very helpful.

That made my day 🙂

Another vote for CodeSite. I've been using a simple collection of functions that wrap it's behavior and it is an excellent, maybe even essential, tool for client-side debugging!

Not sure if this helps, but the TJvAppInstances component in the JEDI VCL collection handles this quite nicely.

I will try this! Any idea why it would fail with that error when I call fdquery.Refresh()?

This is something I struggle with a lot and there has to be an easier way?! I have many projects that have both debug and release configs for win32 and/or win64 targets. Is there a simple way to have the version information THE SAME across all of these? There config options for all builds, all targets, and all configurations, but no matter what I do they all appear to be maintained separately?! All I want it to be able to set my version info in the Project | Options | Version Info | All Configurations section, and have it JUST WORK...