@DbLookup returning more that 65,000 bytes

HCL Domino Domino Forum
1

I have a specific @DbLookup that is used to populate a drop-down in many db’s within our environment. It happens to be an address book that has many entries in it. Currently, it works if no more entries are added. If we add some entries, then all of the drop-downs in all db’s get the following error message:“The specified databsae lookup generated more than 65,000 bytes of results, which is too large for Notes to handle in this context.”

My question: Is there a better way to populate the drop-downs with the large amount of data? Or a better way to handle this situation?

Thanks in Advance,

-Chris

2

Subject: @DbLookup returning more that 65,000 bytes

Hi Chris,

One simple solution to this problem is to avoid using traditional lotus drop down field.

Instead you use a HTML field with tag use your DbLookup to fetch values.

It worked for me in one of my projects in my previous company.

Thanks

Allan

3

Subject: @DbLookup returning more that 65,000 bytes

Use a Custom Picklist instead.

As an alternate. You could have a dialog box with a list box.

Have a button that does a lotus script db search and populates the list box with the names it finds in the hits from the search. You will probably want to turn of Full Text Index to make it faster.

4

Subject: @DbLookup returning more that 65,000 bytes

You can’t return more than 64K so you’ll have to find another way. You can suprress the error message with a [FAILSILENT] keyword I imagine, but that doesn’t help too much

If it’s from an address book can you not just use address dialog for choices? Depending on the address book I guess.

Alternatively use a button and either picklist in formula, or picklistcollection in lotusscript to display a view from the address book and update the field with code.

Just some suggestions off the top of my head

hth

Dan

5

Subject: RE: @DbLookup returning more that 65,000 bytes

even if you use picklist limitation is there (64k)you can do this in two ways

one is split the field data in to two parts

means take the field values in to two fields field a field b

in fielda keep 50 % of data and remaining in field b

in field a if the user dont get value required then add a value other in the field a if user clicks on other make second field visible and hide first field in this way can get the slution i hope it helps you

6

Subject: RE: @DbLookup returning more that 65,000 bytes

Why is there a limitation is picklist? All you’d be doing is displaying a view.

There’d be a limit on the amount of data you can select of course, but that isn’t the issue here

7

Subject: RE: @DbLookup returning more that 65,000 bytes

I’m going down the PickList path and have it working somewhat. I have it being used in conjunction with a Dialog list. The problem here is that the user has to select the option from the view listing, which populates the dialog list with that option(s). Then again select it from the dialog list. Is there a way to get it to populate my underlying form with the initial selection?Thanks,

-Chris

8

Subject: RE: @DbLookup returning more that 65,000 bytes

FIELD x:=@picklist([Custom];@servername:“filepath.nsf”;viewname;“Choose address”;“Choose address”;1)

There shouldn’t be any reason to have a dialog list as well, just set the relevant field to the values chosen

Dan