Most developers know that if you are looking up a value with @DbLookup and provide a key that doesn't exist, Notes will give you an "Entry not found in index" error message. But what about other scenarios? For example, what happens if you look up a key that does exist, but retrieve a value from a field that doesn't exist? Here are several different scenarios:

Looking up to a view that does not exist
This will return an error message of "A view of that name cannot be found in the specified database".

Looking up to a key that does not exist
This will return an error message of "Entry not found in index".

Looking up to a key that does exist, returning a column number that doesn't exist (a number larger than the maximum number of columns)
This will return an empty string, but will not error out.

Looking up to a key that does exist, returning a column number that doesn't exist (a number less than or equal to zero)
This will also return an empty string, but will not error out.

Looking up to a key that does exist, returning a field on the document that doesn't exist
This will return an empty string, but will not error out.

Looking up to a key that does exist, returning a column value that happens to be blank
This will return an empty string (the column value).

Looking up to a remote database that does not exist
This will return an error message of "File does not exist".

Looking up to a remote database on a server that is not responding
This will return the typical "not responding" error message when a server is not responding.

Looking up to a remote database on a server that does not exist
This will return an error message of "Unable to find path to server".