Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

Gas Station Database


pvivacqua

This topic is 7843 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Hello From Brazil,

I am developing a database for a gas station. As the clients finish fueling their cars, records are created and information regarding their fueling such as (total price, type of fuel, price per liter, etc..) are shown in a portal.

Since customers here only pay after fueling, the gas station employee needs to be able to select one or more records from the portal and send their added amount to the "type of payment" database.

After registering the payment for the selected records they should be removed from the portal. Only payment due records should be shown in the portal.

any sugestions?

Thanks

Link to comment
Share on other sites

Hi,

Well in very general terms as I don't know the structure of your db, here is the first method that comes to my mind.

- "alter the key" for the relationship this way, in the related file.

altered ID = Case(paid, Master ID, " ")

and use this field for the relationship. You may need to script the payment into the Line Item though in order for this new field to be indexed.

Link to comment
Share on other sites

Ugo, Thanks for your reply.

Let me show where I am right now to make it a little easier to understand.

I created a checkbox field called "PG" on the related files that are shown in the portal records.

I need to be able to have the user select one or more checkboxs of the records he wants to receive the payment from the portal, click on a button and have the records that are selected, have their amount due summarized and sent to a database called "payment method" after receiving the payment the records should not be on the portal anymore.

Link to comment
Share on other sites

Hi,

When a record isn't in in a portal anymore, it means that it is not a related record !

When a relationship is established from 2 files, you could involve a global field to filter the portal, but you still need a relationship from Main file to Related.

For example, when 5 records in a related file holds ID 0001 and you have an Master ID 0001 in the Main file, you'll have 5 records in portal. Assuming you have another field in related called "paid", create a relationship from a global in the Master (which you will populate with "Not Paid" in your case) and the "paid" field.

Therefore, if 3 records ID0001 are "paid" and 2 are "not paid", only 2 records would show in portal g_paid::Paid.

Drop the related field "Paid" in the portal and switch from "not paid" to "paid" and your record would dispappear from the Portal. But it would still be related to ID0001.

I'm really not specialized in this kind of activities, so others could have some other solutions.

Link to comment
Share on other sites

This topic is 7843 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.