Probably unrelated, but I have noticed that text that has been produced in a
PDF via their OCR tool will have hidden characters in it that will prevent me
from inserting or updating records in my SQL database with that data. The SQL
generates an error as though there were nothing beyond the
I had to do this as well. In the end it was a group that had two fields in it.
I assumed it was a field property that I either could not find or could not
change and submitted a bug report. Since my problem was present in 6.7. or 7,
nothing was investigated.
e
On Jan 30, 2015, at 7:27 AM,
Even setting the filename to empty might be enough. (this way, any
references in the stack that use the stackname won't be broken). When this
is done, when you save it, rather than just saving it brings up the
filename dialog as if it were a new stack, and if you try to save it in the
same place
So far I've determined that stripping out every line of code from the stack
doesn't fix the problem.
Deleting every control does.
Now I'm going through to figure out which control is poisonous to 6.5.2
On Fri, Jan 30, 2015 at 3:40 AM, Geoff Canyon gcan...@gmail.com wrote:
I have a stack that
Is it feasible to make a handler for stacks being opened that would detect
old version stacks and open them copies of them as untitled in the new
stack format while leaving the legacy stack as is?
-- Tom Bodine
--
View this message in context:
well that didn't take long :-P
It turns out that there is one field in the stack -- delete the contents of
that field, and the stack opens fine in 6.5.2.
I copied the contents of the field and pasted into Pages, then deleted the
contents of the field, and the file opened fine in 6.5.2. I then
