Replies: 3 comments
-
When posting the message, I had it proof read by ChatGPT and from its response I asked it to answer the question. And boy, this thing is into SQLpage. It took less than half an hour to get me on track and that's why I reply to my own post: if in trouble, ask ChatGPT. Hey, this would make for a neat SQLpage app, prompting ChatGPT for solutions ;) |
Beta Was this translation helpful? Give feedback.
-
Hello! Happy to hear you found a solution. Maybe you could give a few short code snippets to show the gist of what you ended up with? |
Beta Was this translation helpful? Give feedback.
-
Sure, once there is anything to show up with, I'll be back. But so far I have to rethink some of my GUI to fit SQLpage. And for starters I'm going to set various schemes for my postgreSQL db allowing for better access control. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm currently working with a setup that includes PostgreSQL, pgAdmin4, and LibreOffice Base Forms (LOBF). I realize that SQLPage operates quite differently, and that's where things start to get interesting — but also a bit confusing. My main challenge is figuring out how to begin implementing a drill-down structure in SQLPage.
In LOBF, I use a master form that passes an ID to various subforms, which are then used to display related data. Some of my more complex forms include up to five subforms to show all relevant data for a single item — all editable directly from the form.
Example:
I have a table called prospects that stores information like organization name, contact details, address, phone number, etc.
There’s a many-to-many relationship managed through a table called assignments, which links prospects to campaigns.
Another table, efforts, refers to these assignments and tracks specific actions or tasks.
In LOBF, the form:
Displays a list of efforts (i.e., all tasks due).
When a row is selected, it shows the corresponding prospect and campaign.
Another list shows all previous efforts related to that selected prospect.
Each subform allows new records to be added, which has made this setup incredibly useful for my workflow.
Now, I’d like to recreate or adapt this functionality in SQLPage. However, I’ve hit a wall — mainly due to screen space limitations and the different form mechanics in SQLPage. I feel like I need to approach data viewing and editing differently here, but I haven’t yet figured out a practical solution.
Any examples, suggestions, or ideas?
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions