Quote:Re: table view. I did find some of the problem is I assume in how the fields are defined i.e. a field will sort as 1,104,11,112, ect. instead of 1,11,104,112. That I think I can deal with. Still worried about the functioning of the table view though.
Ah! The famous Text vs. Numbers sorting thing! Your field is defined as a Text field. Change it to a Number field and your values will sort as expected. If your field is defined as Text, Sesame sorts that values as Text, rather than interpreting them as Numbers.
Quote:New problem. I converted a limited set of data from Q&A to a txt file. Tried to import into a form in Sesame and did not have any luck w/ getting the right fields into the right place. One thing that stuck out was I could not import and populate a field set up as a combo box. Am I correct in this assumption.
You can't dynamically populate a Combo Box. If you need this type of functionality, use UserSelect, XUserSelect or PopupMenu instead of a Combo Box.
Quote:Next observation is that I got some major crashing in Sesame
with errors such as
Microsoft Visual C++
File superblock.h
line 181
get NumAvailable() ==0
My only thought is that I did not eliminate (as I did I some earlier imports) some data that apparently Q&A needed
but is very detrimental to Sesame.
To explain: some of the individual records had *** in some of the fields in the txt file. At this point I assume this is a major no-no. Am I correct in assuming this caused the major crashes in Sesame import?
The *** should not be causing this. Something else is going on. Can you give me a description of what you are doing when it crashes? Does it crash on the import itself?