Recent content by SteveF

Those calculations will come later and I agree with you that it's simple arithmetic. What I'm trying to figure out at the moment is how to carry a 'loyalty amount' to the 'clockings' table with the scan of the barcode. Once I have that bit resolved I'll look at the rest of it. It's worth...

The arithmetic isn't really the problem.

In an ideal world yes. If you have an integrated EPOS system then setting a percentage of the sale and using that to form your loyalty bonus makes sense. We're not in that world so we're going to set the amount ourselves as a cash amount and the customer redeems it as they choose. Some will be...

Yes - once the loyalty amount is set it's that amount per drink No - the prices vary but I'm not trying to do a percentage as loyalty. I've never seen it done this way before but am convinced it will work. It's just a digital version of stamping a card to my mind, like we used to get at...

Yes, that's why I was thinking that the loyalty amount would write to the 'clockings' table. If it varied over time it wouldn't matter because the amount is stored in the table and we could redeem it as and when needed

No. If we serve 4 pints we do four scans so they will get the loyalty amount per drink not per transaction

I didn't write it no. It's a database that I had developed for my small business a few years ago. It made sense to me to be able to vary the amount per member if we wanted to, and that form seemed the obvious place to do that.

That's an interesting comparison. It was an inventory database that brought me to Access in the first place. It is similar, tracking balances etc.. I was hoping to vary the amount per member yes but I'm quite happy to use a set amount per transaction if that simplifies it. We've no intention...

Could you say a bit more? Have you found an existing error or a solution to my problem?

I was thinking along those lines yes, we would set the amount as we add new members. The changes wouldn't be important historically no. Looking at my 'Clockings' table it records the date and time of the entry. If it recorded the loyalty amount there then - in my head - we should be able to...

It will be a cash amount so say 30p or something. That would be each time the keytag is scanned so every time they buy a beer they would accumulate another 30p by scanning the tag. They then redeem the accumulated amount at the bar when there's enough.

Hi folks, thanks in advance for help. I have this running now having installed Access 2007 so the first hurdle is cleared. This was designed purely to clock in members and I want to modify it to run a loyalty scheme. Currently it scans a barcode which writes the entry time to a table in the...

Ah, well the idea is that we have some printed keytags and each time you buy a pint you scan the keytag. My thoughts are that I can add a field to this current Entry database that will carry a cash amount - say 30p - and that the 30p increments will cumulate and we can redeem them at the bar. So...

My idea is that the customer scans a key tag which carries a barcode each time they make a purchase. The database was just designed to collect entry data, as in when the customer entered the bar. I think it should be simple enough to add another field to that table to collect a value amount...

Installed access today and the database is running quite happily now so that's the first part of my question very much sorted. I'll have a look at the database over the weekend but am very hopeful that it can be modified to work as I want it to. Excellent progress.