Subject: RE: Cannot Convert Text to number
I’d like you read about the C R I S P Y initiative, and especially read the articles about debugging that this page links to. You have to debug this formula. It might not even be this formula that is causing the problem. There might well be something else about the document and this is just a coincidence of timing.
I suggested it would make a difference in some cases whether the number formatting items were different. Well? Are the number formatting options different for the two users?
I don’t see a place in this formula where you are trying to convert text to a number. This is not the formula that’s causing the error. Possibly it’s the view column formula where the error is occurring.
There are several things wrong with what you’re doing:
If you don’t really need the value to be a number (and it’s not a number now), why not just use @Unique and be done with it?
Don’t do an @DbColumn on all your documents. As the number of documents grows, this will get slower, and slower, and slower. If you must read the last or first value from a column, use LotusScript to read just the last or first value. Fetching back 300,000 bytes of data so you can read the first 5 bytes, is silly.
Even worse, it does the @DbColumn every time the form is refreshed or saved, even though the lookup value is not used unless it’s a new document.
Don’t assign a unique identifier in an input translation formula. Do you really want the value to change every time a user edits the document and every time someone refreshes the form? Oh my god, it does an @DbColumn of every document in the database whenever someone refreshes the form, then doesn’t even use the value. Total waste of several seconds of the user’s time, over and over and over again.
What is the type of the data in the column you’re looking up, number or text? If it’s text, how do you expect @Subset(a; 1) + 1 to work? My suspicion is that the error is coming from some other formula. It might be the column formula.