Search options (Page 6 of 7)

I wanted to share another alternative that also resolves the issue I was having:
.

SUM(COALESCE(tl.fuelGallons,'0,0')) as "TotalGallons"

.
This is basically doing the same thing as your suggestions, but I stumbled upon it in other examples.  Not sure if either of them are better than the other, but maybe someone more experienced in SQLite can answer that one.
.
[edit]
So, coalesce is for when you have more than two values.  In my case, it's only necessary for the IFNULL.  :thumbsup:
.
Thank you again sparrow.

Okay.  Again, I appreciate you looking at it (even further than my initial question).
.
I'm not sure that I follow your suggestion, but I will re-evaluate the data and the structure.  But once I inserted either of your SQL snippets, everything checked out.
.
Thank you for your input!
.
--- Edit ---
.
I'll try to explain my thought process for the structure as they pertain to your suggestion.
.

.
This is intentional because the TRIP table has it's own id_state separate from the leg's in the TRIPLEG table, so they would not necessarily match.
.
There is only 1 id_state in the TRIP table (per trip) and this captures the State where the trip begins.
.
All of the States from the id_state in the TRIPLEG table is to capture all of the points where the truck exits a (and crosses into a different) state.
.
--- ASIDE ---
I have tested other designs where the id_state field is only linked to the TRIPLEG table.  But to me, the id_state fields in the TRIPLEG table represent something different from the one in the TRIP table.
.
Namely- those are all exit points, and the one in the TRIP table is the start point.
.
Maybe this isn't necessary, and this is where I lack experience.  However, it is why I chose to store the id_state in two different tables.
.
But the user does need the distinction, and this is one of the ways I could think of to achieve this and not get it confused in the tablegrid with all the (exit point) legs.
---
.
I would appreciate ANY other feedback.

Derek,
.
Wow, that was really easy.  Sorry for asking such a simple question, but I would have never noticed that otherwise.
.
As always, thank you.  You are a master here.
.
Also thanks for the sorting tip too.  I have noticed sometimes FastReport seems to stutter when it first loads with that much data.

Awesome.  Thanks vovka3003.  That's even more simple than the scripts I have found.

Hi derek,
.
That's what I was looking for.  I overlooked the ReadOnly property.  I was getting it confused with the Enabled property which doesn't allow the field text to be selected.  This way the contents may still be selected and copied.
.
Many thanks!

Hello folks!
.
I'm posting this prior to looking at any of the examples.
The 10 records was just an example here.  I believe the form we use has at least 15 but less than 20.  It is actually oriented in landscape too.  However, none of those details are important, but I'm trying to get an idea for how to implement this using MVD.  I have other projects that will also make use of this technique.
.
sparrow:
Yes, I was considering a temporary table like you described.  I had also thought about capturing a PDF once the order had been processed (and would no longer be changeable). Then removing those excess null fields altogether.
.
derek:
Again, that is exactly what I would like in FastReport.  Do you happen to know which version that is?  If I were to purchase a separate copy of FastReport, would it able to work with MVD (even if it uses the older version)?  I'm sure they have probably changed the file format by now tho...
.
ehwagner:
Thanks for chimming in with the extra cents.  You have me even more curious now with the overlay.  I have noticed that overlay group before, but had no idea how to use it.  It sounds like you have a good example for me to learn how it works tho.
.
sparrow:
Regarding your question about > 10 lines-  You are correct.  The additional lines would go on to page 2, but as I mentioned, it's closer to < 20.  Rarely do they order more than 1 page at a time.
.
I greatly appreciate all your efforts, comments and examples here!

Okay, I was able to find and create solutions to both of my questions. I feel certain that there is a better way to do the blank-line reporting without creating empty records in the database.
.
Derek, I was able to get the signature field in the footer using some SQL. I stumbled around and noticed the Code section in FastReport. I created a variable from there holding the value of the query. But I do prefer the way you mentioned much better. That's exactly what I was looking for.
.
Sparrow, as for more details have a look at the attached example. It demonstrates the reports that I'm after. Namely, a form that matches the format of a company standard form with a set amount of lines. Regardless of the data, or lack thereof.
.
Again, my approach populates empty rows into the database in order to achieve this. It is certainly not the ideal solution, but until I can find another way, this will get me by for now. Hopefully someone else can make use of the example too.
.
As always, I appreciate the help and suggestions!

k245:

I had both tableGrids already using those properties, but thanks for the response.

Derek:

Sorry about the question- it was not clear at all.  You managed to answer it anyway though.

I'm okay using buttons for the first grid, but the second grid must be on a different form with editable properties.

I couldn't figure out how to get the second grid working after the parent was created in the first grid.  I briefly looked at your example this morning.  Once I examine it closer, I'm sure I can figure out the rest.

Thank you a lot derek!
-joshuA

Thanks a lot Derek!
You uncovered several techniques there that I have been trying to figure out. And I had no idea how to do that calculation with SQL either.  I really appreciate it!
I'm sure I'll have other questions along the way