Is this possible....

Sorry about the vague title - wasn't sure how to summarise it down to a title.

I'm basically about to embark on a pretty big database driven project.

As such it will include a table of Products, and a table of Buyers.

The plan is to be able to match Products to Buyers bases on matching keywords. Which I pretty much think I'm OK with doing.

But the plan would be to enable Buyers to register, and be able to view the Products that they had any matches with.

Is this something Security Assist would help with?

If it was all public, it would just be a case of matching on the IDs, but in this case I guess each Buyer should only be able to see their matches.

Does that kinda make sense?

How are you matching the buyer to the products?


What is the relationship and how is it created?

Hi Jason - what I've done in the past is have a structure like this :

table_Products

ProductID
Product
ProductField1
ProductField2
etc

table_Buyers

BuyerID
Buyer
BuyerField1
BuyerField2
etc

tableKeywords

KeywordID
Keyword

tableProductKeywords

ProductID
KeywordID

tableBuyerKeywords
BuyerID
KeywordID

So, for example, when a new Product or Buyer is added, there is also a page listing a load of checkboxes with various Keywords, and the user just checks the ones they want to attach to the Product or Buyer.

This adds records to the ProductKeywords or BuyerKeywords table.

These can then be used to match Products with Buyers where there is a match in those tables.

So the idea here is that Buyers can register and have a profile etc, and when logged in be able to view the Products where there is a match.

Does that make sense?

OK, when a user logs in with security assist, the users ID is stored in a session variable.

This user id can be used to create the relationship between the selected products, then used to filter the recordset to display them


The userlevel authentication tutorial on the security assist support page talks more about the session variables that are created on login, how to add them and use them in creating page access rules.


the sessions can also be used when creating recordsets, see the profile page for an example, and in the insert record and update record behaviors.

Thanks Jason - sounds like it should be possible then. I'm only just about to start the project, so it'll be while before I get that far.

I'll have a look at that tutorial though.

you're welcome.