Web NEWBIE

[aprescott]

So I am working on "converting" our existing Desktop database to Web-based by recreating everything and trying to achieve similar functionality. Teaching myself as I go along, and scouring the forums for advice where needed.

This may be a dumb question, but I can't seem to find the answer anywhere (or at least I don't speak the language of web apps well enough to know what I'm searching for)

Current set up:
Converted my DBF tables to SQL tables. Setting up a grid with detail view to use as the editing form for our contacts database.

Desired behavior:
Would like to be able to open another form (UX?) from a particular record to modify data on a connected table (the equivalent of a one-to-one set in Desktop) and not sure how to ensure it is linked to the same record.

Used the SQL statement to emulate the set structure we used in desktop:

SELECT
*
FROM records records
LEFT OUTER JOIN volunteer volunteer
ON records.ID_NUMBER = volunteer.RECORD_ID

Tried creating a new grid that lets me include the needed fields from both tables, but it'd be great to be able to click directly to the new form(ux?) and it be already queried to the same record.

I am not sure that is making any sense. Some guidance of a direction would be much appreciated.

[madtowng]

Your courage to convert everything is admirable.
I can help, but my abilities vary depending on which sql you use.
With that said, I think I do a lot of what you're wanting to do.
The image attached is a simple grid to keep of our vehicle assignments.
A dispatch simply clicks on UnAssigned on the far left, which brings up a UX to choose the driver,
which then records the information , including the time and ip address it was done at to the appropriate tables.
To un-assign the driver from the vehicle, the dispatcher clicks on the driver number, and is presented a UX to
confirm the information.
Let me know if my thinking is right.

On a side note, assigning an alias to the table is not required, but often done for usability and to make the code easier to read.
You are allowed to do something like the code shown below, although hopefully you will be a bit more selective about the columns
you select.

Gregg

select d.*, v.*
from records d
left join  volunteer v on v.userid = d.whodoneit

2021-02-18_18-30-18.png

[Lance Gurd]

A word of advice, ditch grids. Start your web journey by learning lists, or if you are a bit more confident with some programming viewboxes

[Jay Talbott]

Another word of advice (and remember free advice is sometimes worth what it costs you, but in this case, it will be worth much more).
Join IADN ( https://iadn.com/ )and listen in on the Friday webinars.
You will be glad you did.

Jay

[aprescott]

What would be your recommendation on handling sets? We used quite a few in our desktop application, and thus far trying to recreate that functionality in SQL terms has been the most confounding. I keep seeing people mention "Views" and SQL Joins, and I have dabbled with this, but I am not get the desired outcome.

[madtowng]

My opinion is that SQL handles the functionality of sets much easier and faster.
As I thought about, I didn't give much of an answer.

A set is the combination of 2 or more tables that have some kind of relationship (Customers of salespeople, orders placed by customers, supervisors of employees). where you use/display the data based on your requirements. SQL views do this very well. The code you initially showed is basically as a set.

[aprescott]

Let's say I have a one-to-many set in Desktop.

Donor->Contributions

One particular donor can have many contributions. In Desktop, I had a one-to many set. What do I do in web? (Keep it basic for me, I am still new to this)

[madtowng]

I can do this, but can you supply some sample data. It would make it much easier for me to create an example that hopefully makes sense to you.

[Russell Craycraft]

I second the ditching of grids and converting to lists.
I also second the joining of IADN.
If you need some help with creating lists, detail views, and search options. I can offer a little time this weekend to quickly get you going.

[madtowng]

Hi Russell,
I haven't been pushing the list or viewbox control because (at least in my opinion) they take longer to create and are not as easy
to create the functionality of a grid.

I will admit this is partially due to several failed attempts to produce a list in under 5 minutes that displays my data and gives me basic
search functionality.

If your offer for help with lists is open to participants here, I can certainly use some of that myself.

Thanks for reading.

Gregg

[Russell Craycraft]

madtowng,
I can certainly help you with setting up a basic list. Do you have Skype or Zoom?

You can email me at [email protected] if you'd prefer.

[Russell Craycraft]

I am lucky because I was late to the Alpha party, and came in during the "Lists are good, Grids are bad" movement, and also the "Don't use TabbedUI's, use UXs and PanelCards". Now I am familiar with TabbedUI now, but agree they are not ideal.

[RobPolley]

I'm not new to alpha, but I'm new to lists and to sql. I second Jay's advice, to join IADN and attend the Friday webinars, and I also recommend an online sql course. I used udemy, but i look at w3 schools frequently. IADN has videos of the Friday webinars, that are helpful, as are swylens (sp) videos, which are in the alpha help system. It's a journey. Good luck.

[aprescott]

I actually joined earlier this week and already the webinar videos have been extremely helpful!

[Russell Craycraft]

No bs, down and dirty sql youtube videos...(My favorite)

https://www.youtube.com/watch?v=nWyy...F1U90Ee1Ecb5tt