I read in the help that the maximum data that can be returned by @dblookup is 64kb. I have a web app that returns data and sometimes (when returning large amounts of data) I get an error "HTTP Web Server: Lotus Notes Exception - Field is too large (32K) or View’s column & selection formulas are too large ". What happened to the 64k limit?
Subject: @DbLookup 64k limit
That message means a field is too big in one of the docs.
If the contents of the field is not essential to the view, exclude it from the view.
Subject: RE: @DbLookup 64k limit
The return value of the @dblookup is a text list. When the list goes over 32K, I get that message. If I remove an entry from the list and it goes down below the 32K limit, it works. There are no extra fields in the return string, I have it down to the bare minimum.
Subject: RE: @DbLookup 64k limit
Subject: RE: @DbLookup 64k limit
File Save, Thanks for the website, good reference. This still puzzels me though. Lotus says in the help that @dbLookup can return 64k of data. According to geniisoft, they think there is a 64k+ limit on the number of characters in a computed text field. I am getting a 32k limit warning. Where is the 32k coming from??? I have just accepted this as a limitation and I am moving on (with a new error handler in place) but it would be nice if what Lotus wrote in the help matched what was actually happening.
Subject: RE: @DbLookup 64k limit
You should not say “according to Gennisoft”. Ben has that document there as a convenience. He did not author the document:-)
The limit is not on the number of characters, but on the size of the data being returned.
Subject: RE: @DbLookup 64k limit
Sorry, didn’t mean to implicate Gennisoft. My bad. I realize the limit is on the size of the data. My beef with Lotus is that the help says 64KB and the server errors at 32KB.
Subject: RE: @DbLookup 64k limit
Why are you having a beef? You are running up against a field size limitation that is independent of the amount of data that a DBLookup can return.
For example, I may use a DBLookup in a tmpVariable (and get 64K back) and if it is over 32K, parse it out to different fields.
From a practical standpoint, any one field that contains over 64K in data is a pretty useless field (if being displayed).
Subject: RE: @DbLookup 64k limit
Once again you are right! I had it in my head that the 32k limit error was being generated because of the lookup, but in reality it was for the field that it was writing to. I must say however, your assesment of a 64k field not being usefull for display is incorrect. I am actually using it to display a shopping cart on my website and it works quite well. (It could be prettier, but at least I didn’t have to use a table.) Alas all this is going to be moot soon as we move our website into WebSphere… Thanks for your help though.