I have searched the forum but no one has posted any problems with XPOST.  But I have been spending hours trying to make a successful XPOST of numbers to no avail.

If I am posting a string to a string field it appears to work OK.  But I have been unable to post a number to a number field.

The XPOST process actually is working, I am not getting an Error message, but the original values in the destination elements are wiped out to 0

Examples are here:

Quote:
This line posts OK, vItems is a string. and destination "Items" is bound to a string

Quote:
This line zeroes out the destination "Locn".  vCount is a number, and  destination "Locn" is bound to a number.

I have used @ToNumber(vCount) to make sure it was a number.  I have tried converting the number being posted to a string with @STR(vCount) and that does not work.

Originally I was trying to replace the value in Locn.  Having problems, I ended up using the following values for final operation option : "ADD", "REPLACE", and "".  All trials end up with a value of 0 in the destination field.  "x" and "vStock" are numbers and the ID elements are bound to numbers.

I have used WriteLn in a number of places to confirm all the variables are correct.

I have saved the DSR to another DB, same results.

Has anyone else had this XPOST problem with numbers?

The response to my problem:
Quote:
Thank you very much.

I would like to repeat a request made on 12/29/03:
Quote:

This is ridiculous to have to spend hours of time trying to use features that are known not to work!  What other functions have problems? I am sure there are over 40 functions that I have not tried to use yet.  I cannot continue to waste hours of time that I can never get back.  And that waste could have been prevented.

Your honesty is commendable, you don't have to admit it is known, you could say thanks for pointing that out.  I respect that, but I am also expecting you to look out for our interests as customers. 

This is not a beta testing cycle.  We have gone through almost 3 years of testing.  This is a released purchased product and I think that we have a right to know what does not work.

I have been holding back many issues, trying not to be negative.  I feel that responses to my observations are defensive and have become adversarial and so I have avoided asking questions.  I want this forum to be a positive upbeat area for cooperation.

Being told that a problem is already known, and that it has been corrected in the next release does not help deliver products that are due or overdue already.  And then there is no projected date for next release.  There is no patch being offered until the next release is available.  I have commitments to my clients and you are making your problems into my problems.

Many people are using Sesame for themselves, but there are others like myself who have planned on using Sesame to develop solutions for other end users.  The tolerance level has to be lower by necessity.

Sorry, I am rambling.........back to the issue:

======================================
I would like to see a list of know problems, 
What are the workarounds?

You must have a list of what is being corrected in 1.0.2.  This could be used as a minimum list of Know Issues.  Each item could be categorized as a Fix to a Known Problem, an enhancement to an existing feature, or a new feature.  You also have a list of items that will slip into the following release, and that is added to daily.  Some of those are also Known Problems.

I have done everything I can to make this product a success, maintaining a loyalty to the Lantica staff, avoiding any public negative comments about the product, but I am highly frustrated at the moment.    And I have already waited eight to calm down.  My original posting was at 6am in the morning, up all night because I was trying to diagnose this specific issue and make it work for presentation today.  (Now postponed till ?)

I was thinking of making a limited list myself by searching the forum and making a database of "Known Problems", creating a topic for this, and trying to maintain it.  But I don't have time to do work that can be and should be done by others.

We don't need to know about planned enhancements or new features, just need to know how we can use our time more effectively.

I apologize in advance if anyone at Lantica is offended.  At this point I am just venting, so more defensive comments are not needed.  I would just like to see a real list of Known Problems that is maintained. 

Lots of ways to do this:
1.  Make a Sesame application on the WebSite that we can browse. 
2.  Make a Sesame application available that we can download.  Post a notice when it is updated. 
3.  Or send as attachment to those who request to be on the mailing. 
4.  As a minimum, provide something on this site that we can read and monitor.

Thanks for listening.  (Maybe tomorrow will be a better day).

Bob, I knew this was going to come from you!! Unfortunately, this is confluence of many things to go certain way to lead to this kind of problem. Most of bugs are somehow uncovered during the discussion on the board. This being an exception, it probably reported through e-mail or support phone call, so it did not come to the notice of this forum.  Moreover, version 1.0.2 is probably ready to come out any day now and if it would have been out, this could have been avoided.  All these could have happened in very short frame of time and updating the list of known bugs could not be done before you toiled your way through this bug. You might have also pushed a little too hard to make it work and did not think that it could be a bug. Erika did respond very quickly, honestly and openly without any reservation. Good part is that now you know xpost command inside out and i have yet to learn and use it.  

Quote:

In this particular case, the actual bug which is "known" was tracked down about two weeks ago and looks something like this:

The do_command loop is allocating only 2048 arguments. This limit may be exceeded by certain operations. Changed to dynamic allocation.  

When Jerry contacted Tech Support, we made the connection that his problem might be a side effect of the behavior above, because we'd recently been looking at it in response to a different issue. I can only apologize for not making that connection in your case, Walt. When we fixed the problem, it didn't really occur to us that your earlier problem was related. Since your post talks about compile speed, rather than crashing, I'm not sure it actually is related. I assure you that Mark and I are not deliberately attempting to "fool" you.  I dearly wish we had the luxury of assigning someone to dedicate all day to updating various lists, web pages and reference materials, but we just don't. Mark and I take care of those maintenance tasks as we get a chance.

Again, we understand that it's frustrating. We promise that we will try to dedicate more time to making sure that you are kept informed, but I hope that none of you truly believe that the same people who dedicate so much time to watching this Forum for people having trouble, to implementing many of your fixes and feature requests within hours of your requesting them and to making sure that you have a direct channel to the actual developers are somehow interested in deliberately wasting your time.

Speaking purely personally, I'm saddened by the implication. We expect that every user isn't going to like every technical choice we make, but I  have always tried to be available to and above board with this user community, far more so than many developers, who put layers of marketing people and gatekeepers between themselves and their users.

I'll make every effort to get the Known Bugs page updated this weekend, although the 1.0.2 release and accompanying change log is higher on my priority list right now.

I know there is always room for improvements in customer service.

I know that there are always better ways to accomplish a task.

I know that you can only try to attain perfection not get perfection.

I also know that I have NEVER met a group of people that care so much about what they are working on as the people of Lantica and the people trying to use Sesame. It is amazing to me how much everyone, developers and users care about getting the best results. So even though people get frustrated and people get upset it just proves to me that the people on this forum care more then most and this will only lead to a better result for us all.

As far as the Lantica team goes , I wish my customer service did half as good a job as you guys and gals do. I have never worked with an organization that even comes close to the level of support you people offer.

And to anybody out there that is about to accuse me of being impartial or anything worse save the effort of writing. It is truly the way I feel.