Post your feature requests and suggestions on our forum Groups
Cont_bg



Just a suggestion for whenever you have some extra time —

A powerful way to filter database results is to be able to use the User ID and/or Password option as the filter.

I create a form that includes, among the other fields, a User ID and Password.

In the database widget I make the User ID and Password field not visible, but the results are automatically filtered by the Password field during login.

In this way I can provide access to a single database and at the same provide data only to those I want to see it.

29.11.2010

I forgot to add that the database is password protected using the security component in the widget builder and the filter (the password is best) is activated when the user logs into the database.

29.11.2010

Hi, Russell

To be honest, I didn’t understand your suggestion.
But it looks like we can do it right now using Team module.
Have you seen Team button on Records page?

You can create Views, using Search or Filters or Grouping, save it and use Team for this Views.
This way you’ll invite people to MTH to work with your Views.

Wouldn’t it do what you need?

If no, please, explain more in details your suggestion and maybe provide me with some screenshots.

Thank you!

29.11.2010

Igor,

I was just typing a more detailed explanation and realized that it wouldn’t work, because the MTH system doesn’t support multiple User ID’s and Passwords for a single database.

The work I do is best supported by embedding everything in my websites rather than bringing clients into MTH.

Creating filtered views and being able to generate a link or embed code is a good solution.

But, a more flexible, powerful solution is to filter on the fly using the password protection functionality in the widget — User ID and Password — with User ID as the filter. When a user logs into the database, only records associated with that User are shown.

For instance —

I create a Training Form that includes the field: Your Supervisor’s Email among the many other fields.

I make the database password protected (this would only work if I could assign multiple User ID’s and Passwords) assigning four different supervisors unique User ID’s (their email) and Passwords to access the Training Form database.

When a Supervisor logs in to the embedded database, only those records that include that supervisor’s email (which is the User ID for the login) are included in the records shown.

In this way, I am able to provide a single access to filtered database results.

29.11.2010