Ceterum censeo, it is about time to make database reports editable - id est,to have a two-way link between any user-editable fields (data records and PIO input) and the listing in a report.
I make do with named objects and scripted reports (a normal line for each entry) & returning data, but a normal user cannot be excpeted to do it this way (and I hate writing scripts for the purpose.)
Surely, it can't be that difficult - GIS progams such as MapInfo have been able to do it for decades (called exempli gratia 'browse table.)' Right - there is no persistent internal object ID in VW? Well, introduce the concept. At least I surely could use this every so often in my scripts.
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Question
Petri
Ceterum censeo, it is about time to make database reports editable - id est,to have a two-way link between any user-editable fields (data records and PIO input) and the listing in a report.
I make do with named objects and scripted reports (a normal line for each entry) & returning data, but a normal user cannot be excpeted to do it this way (and I hate writing scripts for the purpose.)
Surely, it can't be that difficult - GIS progams such as MapInfo have been able to do it for decades (called exempli gratia 'browse table.)' Right - there is no persistent internal object ID in VW? Well, introduce the concept. At least I surely could use this every so often in my scripts.
Sat sapienti.
Link to comment
0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.