Search options (Page 4 of 7)

Hi all,
.
I wasn't planning to check for duplicates on the groups, but I wanted to see how far I could go... not very far
.
The other duplicate checking examples that I found were dealing with a single table.  And this takes it a bit further, or either I'm over-complicating it.
.
I started the code, but this may not be the ideal approach.
.
Thanks in advance for having a look.

Hi again,
.
So after further experimenting with derek's first option, I would like to clarify something, which is why I prefer the scripting method for this...
.
Changing the TabIndex property within the PageControl, is the same as selecting that tab in design mode.  Thus, the tab that was last selected becomes the tab that is first shown when the form loads.  So the TabIndex property in the PageControl is not fixed because it also changes to the tab that was selected prior to running the project.
.
To me, this is not really "setting a default".  Because while I'm designing a project, I don't always go back and select the tab that I wish to show when the form loads (mostly because I forget to do this).
.
It would be nice to have this option without scripting though...
.
Just my two cents

Thank you sparrow, that's precisely what I am after.  I'm glad this can be done.

Hi derek,
.
Just to recap on my latest post in here.  I'm not loosing my mind (yet).  I had this figured out already.  But now my users are asking for date and time ranges, so I had to revisit some past posts here too.  That's the reason for the seemingly revisit to this issue (again).
.
I experimented with your solution some, and it is possible to use a cfField to do what I needed (thanks to your example). However, one thing I noticed with my second requirement mentioned below; you cannot share form controls being used for the Date/Time field when the date and time are being used separately.
.
So I come to this conclusion (guideline):

• When there will always be a date with an optional time, it can be done using a single date/time database field.

• When both date and time are optional, this requires the date field and time field separately in the database.

• There probably are some other cases to be included here too...

.
I wasn't aware of these, and it always bugs me when I open the database externally and see a perfectly good date/time combination using any of the three MVD fields: date/time, date, or time.  I'll just have to mentally ignore my OCD here.
.
Anyways, my apologies for stating the obvious to those more experienced.  And as always derek, I appreciate your examples and advice.

Awesome Agilefalcon,
.
I didn't realize there were that many other options available.  But then again, I haven't really looked much further than MVD- once I found it
.
I briefly looked at the VisualNeo website, and if DMITRY decides to part ways with MVD then that will be my next option.
.
I don't consider myself a programmer, but I enjoy the challenges of learning how things work (and creating things from it).
.
Thanks again for taking time to comment

Well, I'm reconsidering my suggestion for commenting now
.
I've been enrolled in a few programming classes over the past year or so.  And I realize these are entry level courses, but they emphasize heavy commenting on our code.  We get penalized otherwise.
.
I guess there is a fine line here because Teco would fire me
.
I appreciate the feedback and also for the references.  And thanks to derek for being sypathetic on us

Hi papafrankc,
.
I wish I could offer you some useful help here.  But I run into this same thing all the time (it seems).  I'm always tempted to write sub-procedures for repeated code, but then I start redesigning my forms to help compensate instead.
.
I can't see your whole project, but for me I try to separate forms (which derek has suggested, in some of my cases) instead of trying to capture all kinds of variations.  Again, this may not apply for you though.
.
Commenting is your best friend, which you are doing, so I think you have the bases covered.  I start commenting almost every line when it starts getting too cluttered.  Because when I'm going back (months, or years) later it's easier for me to read my notes instead of converting what the code is doing in my head. 
.
I will be curious if others have better suggestions for you with this too.

Okay, so moving forward.  I'm starting to build multiple save buttons depending on where the frmAtt (is called) originated from.  What's the best way to handle this scenario?
.
I found this post doing a similar thing with labels, but I'm stepping into unfamiliar territory here...
.
Depending on where the form is called, I want to hide certain controls because they're not applicable.  The project I've attached is a simple example using ShowMessages to demonstrate my idea.
.
Currently, I have two different places where the button is called, and I need to hide (or do something special) for each case.  The Apply To Group button is one instance. When the new record button is called from the frmEmp it needs to do something different.
.
To me, this seems like I may be over-complicating things, and I feel like there might be a better way to approach this.  Would someone offer extra advice here?  I would appreciate it.  Any thoughts or ideas?

Sub-thread title: Add child records to parent records listed in the TableGrid

Hi folks,
.
Instead of creating another thread, I'm continuing this one since it uses the same project.
.
So, I'm progressing a little further with it, but I could use some more advice before I implement it into the working project...
.
The interface is working as desired:

• Once a department group is selected, then the Apply to Group button allows for a mass update of attendance records for each one in that group.

• The cyan textbox is showing the parent IDs to add new child records for.

• I'm not sure if it's necessary to create a separate (identical) form for this case, but I did.

• The MessageBoxes are temporarily shown, of course, as an example.

.
I don't recall anyone else on the forum doing or requesting this.  But as of right now, I'm thinking of using a script to loop a SQLExecute for each ID in the tableGrid to create the appropriate child records.
.
This is my idea for how to approach it, but I wanted to get some outside opinions first.  Is this a good way (notice any flaws?), or suggest a better (more simple) approach?
.
Thanks!

Thanks again cfDerek
.
Up until a few minutes ago, I thought I solved it using sparrow's steps.  But it turns out that I was using a different PC, and evidently the date formatting on that PC uses a slash / as the date separator (so I thought it was fixed), and on this PC it's using the dash - instead.  However, this is a tedious detail that I wanted to point out.
.
So the cfField is the best way to fully control the formatting here.  It's kinda interesting that FastReports ignores the special formatting characters explicitly defined within one of its own field's property settings though.  But, I guess this falls into one of those controlling the interface arguments.
.
I'm starting to see now-  the reason for your new nickname.

Hey sparrow and derek,
.
As always thank you for the suggestions!
.
derek is all about those calculated fields   I was experimenting with that approach as well, but I couldn't get it working.  Forgive me for not throwing together an example solution for the question.  And MANY thanks for providing us one here!
.
I was able to get both of your methods to work, but I had to do some minor adjustments with sparrow's code because it kept throwing an error about the report field not being a valid time.  I don't fully understand the syntax in FastReport with the brackets <> and [] and ().  Because of this, I get unexpected results usually.  Anyways- I managed to get it working.
.
I really appreciate it guys!

Hi prahousefamily,
.
Someone else might be able to help you with the checkbox part.  I have not seen that done before as a tableGrid control-  though I would be curious if this is possible as well.
.
As far as changing the values presented in the tableGrid, this is one way to do it.  Create an extra calculatedField in your table containing this line:

case boolField when 1 then 'aaa' when 0 then 'bbb ' else '' end

.
Changing the boolField to the name of your actual boolean field, and the 'aaa' and 'bbb' to the values corresponding to the 1 and 0.
.
Hope this gets you started,
-joshuA