You should be able to open the class that the button bar is found in and change the Caption property. They could also be changed at runtime in the Init method with this.Caption = "whatever you want", but it's better to just change it in the class. Might need to include a dodefault() command just...
You can also start Excel like this if you are opening a file:
oWB = getobject(this.FileName)
oXL = oWB.application
oWS = oWB.Sheets(1)
Then you can do this:
CellVal = oWS.Cells(1, "A").Value
Not sure about 32 vs. 64, off-hand.
CAST and the simpler method suggested both work. As always, it's about preference and also about some drawbacks to one or the other as Chriss points out. Personally, I'm usually using the simpler method of "0000.00 as SomeNumber" using the appropriate number of whole number digits and decimal...
I've used it to create responsive HTML with CSS for a project I'm working on. It's been working well. I've had to modify the requests a few times, usually, to get them to work better. I can say "modify the last solution so that . . ." and it works quite well. I'm not sure it could write a full...
Mentioned, perhaps indirectly . . . do the fields in the report have an alias in front of them for their data source? They shouldn't, generally.
Also mentioned is how the comparison works. An alternative is this:
FLen = len(<TableName.FieldName>)
for upper(<TableName.FieldName>) =...
Looks like you got some answers, but I don't think there's a way to know what you want to know, at least in a short amount of time. If you send a request, you have to deal with the timeouts, which you can control, but that's of limited value. The vagaries of communication across the Internet...
That's long been a problem. It's frustrating when VFP crashes or the computer reboots for an update and you lose those commands. The 64K limit has also been bothersome. There are likely solutions like setting up a macro to save the command history to a file (besides _command.prg). Also, you can...
Well, I lied. I got some tunnel vision going. The left joins were in there for the main relationship (invoice header to line items to parts), but there was one other relation to bring in a bit of other, minor you might say, info and I wasn't spotting that as needing a left join.
I'm confused by your response, but the simple answer is that I'm printing a blank invoice and the invoice expects something in the fields for line item details. That data can't just not exist. The other simple answer is that I got it working as I'd originally expected.
Ok, but in that example you're not left joining, which would be required (or right joining, depending) and you're not using NVL. So that works in my standard case where the invoice has line items, but not in the outlier where there are no invoice line items.
I have the left joins in there. There is no doubt about that. I don't see behavior that works when it's Parent --> Child --> Grandchild even when left joining Parent --> Child and left joining Child --> Grandchild. When it's only Parent --> Child, then it's easy.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.