I was just wondering if anyone knew if @dblookups will be allowed in views in future releases.
This would be a great help meaning you could use notes as a relational database and remove the need to store the same data on multiple forms.
At the moment i just catagorise the different documents together or store the needed data on multiple documents, but some users understandably want it shown on one line.
Subject: Dblookups in views in Future Releases?
Query Views in Notes and Domino 7 will do joins, but they require that you use the DB2 back-end option.
Subject: Actually Stan, I don’t think thats true. The performance will be bad, but I believe…
That the Backend datastore is completely independant of the NIF elements.
Subject: RE: Actually Stan, I don’t think thats true. The performance will be bad, but I believe…
That’s not what the release notes say (see: IBM - United States)
AFAIK, both Access Views and Query Views require DB2NSF or “federated data”.
Subject: Then how does it work locally where all data is stored in NSF, not DB2?
Subject: RE: Then how does it work locally where all data is stored in NSF, not DB2?
I don’t know that it does, Bill, unless the index needs to be created on the server before replicating locally.
Subject: Dblookups in views in Future Releases?
Michael, have you tried using NotesSQL?
Or even in Notes, you can create a form thats a report that is almost ‘relational’. If you built you keys properly you can load a primary key of one form, then loop through each key to load the values stored on a ‘related’ form.
I do this all the time using @for and @dblookup. The only thing is I cannot use a single view, rather I use two views and display the contents in a form using fields.
Its tedious but it works.
HTH
ST
Subject: RE: Dblookups in views in Future Releases?
I haven’t tried or heared of NotesSQL Could you elaborate.
I all ready use the method you mention but in order to have uptodate data means a slow opening view. I assume relational elements in notes would be a lot quicker.