Hi all,I have a field that looks(@dbcolumn) up customer addresses.
Users were happy with the dialoglist where they could type the first character and comma & the entire name came up. Since now the addresses have overshot the 64KB limit they got the error msg…“db generated more than 65000 bytes of data”
Now i cannot have a picklist since i cannot use it in a field since it goes in a loop & throws up dialog list even after i select some value from the list…
the other way was to use Names & “use viewdialog” for choices.now this has many probs like retaining selected data,no type ahead…
users have been complaining a lot…When will this 64KB limit be eliminated?
can someone give me an idea of how to get around this problem and give the same functionality of @dbcolumn & type ahead…
many thanks
Subject: Nasty legacy
Hi Dorothy,the 64k limit is an old legacy, that never has been removed (wich might make sense sometimes since it prevents performance desasters) and you don’t have that many options. The view dialog doesn’t retain the selected values and you can’t influence the sizing (that’s a blooper). What you could try:
- Use a popup form with an embedded view
… question here: how to trigger it
-
Define a secondary addressbook in Notes and make the customer field a names field. This secondary addressbook actually would be your application with customizes ($Users…) views. This way you can use the standard address functionality. Downside: Lookup happens against the Domino Directory AND your application.
-
Simulate a selection using views. There was years ago a notes advisor article about it. You should find it there.
Hth
stw
Subject: RE: Nasty legacy
Thanks…I cant opt for the secondary address book since the adress book is just part of a large application.
However I would be interested in the simulation using views. If u have any ideas abt it pls help me.
Thanks
Subject: Options for using views
Hi Dorothy,The Dialog list roughly gives you an idea where you can head with views… I’m not fully sure if my idea can work out, so users would be pleased. So I throw the concept to you and you give it a shot:
a) Create a form that has the view embedded with the data you want to select from
b) have fields in the form that reflect the already selected names and/or vaules. Show them as Checkboxes, so the user could deselect values. (This requires some tricks: have a hidden field with the values and point both the default value as well as the value source of a visible checkbox to it.
c) Popup this form using dialogbox in Lotus Script. You also migh use new document (you later do not save) to store the values before popping the box).
d) have a button on the view that writes the values from the selected document back into your popup document. When the user presses ok, then you move the values back into the original document.
I haven’t though fully through on the button’s code. You might need an profile document as intermediate (view writes into profile, doc reads from profile or so).
This way the users need to press a button to get in the dialog (certainly worse that before), however it could be close…
Something else you might consider: It is VERY likley, that most of your users most of the time do not need ALL of the names. So if you can change the logic of your dblookup to produce only the “most wanted” (for that specific user) and provide a button with: “Lookup other names” with a viewlist, you might actually make the users most happy!
Ask as much as u need, and let me know how it worked. If you want to email me, look up my name in Google. It’s the first hit.
I’m glad to be of service.
stw