Most likely, the form creates the alias but report set to private data session, like you said. Even though I don't understand how what did he mean by able to preview it but running the form it doesn't work. Seems preview in design mode, not GUI
Completely agree. I would go even further and I would create an updatable view, browse it first and if I like what I see, DELETE ALL==> TABLEUPDATE()===>Requery(), unless FoxUp is not familiar with views
If you need to sort a view or a cursor, you can add an additional field to it INT(VAL(grade)) AS igrade_sort. If you need to order a table then you need to create an index, like it was suggested above. I am using it all the time
Maybe I am missing something but if you have the totals already calculated on the form, then you don't need any report totals, just correct groupings on report and display form totals as a variables. Otherwise, you will need to create multiple groupings on the report and create report totals for...
I am confused by your explanation. If you need a single record from the parent, why would you need any detail in the first place? The only thing you would have from detail or child is some kind of amount if you group and the rest of information from the child will collapse to the last...
Well, you have very valid responses from other users and I completely agree with them about this very strange request. Report with 300 fields on one page? That would be pretty hard to implement. But if you still want to do it, the suggestion to create a bogus cursor with a number of records for...
As long as those variables are public or global and the report has to be set with default data session. It's a bit weird, quite frankly. I don't see why you can't create a cursor at least with the fields selected on the form but without more details it's hard to day
Completely agree. We have the same thing when the same user can open the same form from multiple sessions of the same data, that is not a problem at all. The only thing we do is locking up the processes that create transactions: billing update, payment update etc. But maintenance form can be...
We use textreport class library, my former manager found a long time ago. At that time our clients used DotMatrix reports heavily. This class is awesome, you can print any text you want and customize it. All our FoxPro laser reports have an instance of this class if the user selects to print to...
Hello,
like I said, it's your app, you can design it any way you want. I was just saying that normally you don't use combobox, if the user need to chose from more than 20-30 records.
As far as views, I write my own SQL views statements, meaning I do not use FoxPro view wizard. We still use...
You c an design your forms any way you want but, in my opinion:
1. I would never use tables as a source for anything, only views. They can be open exactly the same way as tables can but it much safer than to use tables directly.
2. 2000 records in the combobox???? Have you try to pick a record...
Not my code but check the VALID() in the LostFocus() is a bit weird, I don't think you need it. If VALID() = .F., the cursor will never get into the LostFocus() anyway
Yes, that is all correct. Valid() is better but LostFocus() will work as well. I think the problem with the original code is that there is no test at all. And, yes, IF EMPTY() without CTOD() should work fine. Another issue I can see with all that is that returning .F. from either method will...
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.