Well currently I am testing out the wireless network that I set up yesterday. Browsing the internet wirelessly thanks to  the router sitting 2 feet behind me and at the same time pulling all my e-mails from the computer that I was able to rescue them to, on the wired network. Two network connections is kinda cool.

Right now I'm going to try to link all the e-mail files back into the e-mail program.

-Ray

Glad you reminded me Mark......

Could really some type of HTTP Put and Get tools to use with web page forms......... but knowing you, that is probably already done or in the plans, right?

Hint: The correct answer should be YES.

And Happy Belated Birthday    

Well today I decided to to try and eliminate or at least minimize the floating point errors in @Round and @Decimals. As it stands right now both of them have been rewritten from the ground up and as far as I can tell, the few problems that I was aware of are fixed and I have not seen any new problems.

-Ray

From the code that you posted, the software you are using appears to be a kind of HTTP client (like wget) that acts similarly to a web browser in that it posts HTTP requests and receives replies. The question is what kind of software is at the other end.

Are you asking for Sesame to act as a HTTP client (a program that posts HTTP requests - as seen above), or a HTTP server, a program that replies to such requests (the machine referred to above as: "www.server.com")?

I think POST is doing something as basic as going to a web site, entering the URL, filling in the fields, and pressing SUBMIT, and capturing the reply that the webhost sends back as a reply.

GET is just capturing the page.

Both are done without actually opening a browswer but making another type of connection (telnet?)

Again, not my area of knowledge, I am just a happy user of the tool, and would like to see a similar function in Sesame.

An example of using this, would be able to enter a zip code into a  LE, and execute the HTTP command to go to the USPS.com site, pass in the zipcode, and capture the page that comes back with the city and state info.  I could now parse that returned data to extract the city/state that I wanted.  This is a simple sample, but it could be more complex, filling in many fields on a web page and pressing submit, without the need to open a browser.  Login names and passwords can also be passed, making a simple one-button click on Sesame, and never leaving the application.

Thanks for listening Mark.  I did not mean to hijack the thread on your original subject.  It was your mention of interfacing with other products that got me started on this.

I am still confused when you say Sesame will noever respond to request as a webserver.

I am asking for Sesame as a webclient to SEND a request to a webserver which would respond back to a text file or even better as a user defined Sesame variable.

I will drop the request for now, but thanks for listening. 

Back to the original subject: In the continuing saga

Thanks Ray.....

I think I had a handle on what he was saying, and can understand the confusion.  I already pleaded guilty to not being clear.  I have sent Mark an offline email about the subject.  His thoughts to provide the ability to function as a webclient is a great idea. 

But rather than another programming tool, another language to learn,  I am looking for a simple function that does not require me to write more programming.  This HTTP function already exists in one other competitive database program that I know of.

It would be convenient to show the Sesame functions to my clients with the Sesame documentation, and help teach them to use the functions.  But when I come to "special" functions, I will have to say, "These can do a lot for you also, but you need to learn another language (cgi, perl, HTTP, java, VB, python, etc)  to use them."  They will not be used.

We are all willing to learn Sbasic, but would like to see the function library built up so we only need to learn syntax and not new languages, DLLs. API calls, libraries, etc.

Again, too much time on one request.  I will continue to make my point offline.

=================================
A reply the other day said that most Sesame databases are flat file designs, without subforms.  This would suggest that most users are not as technical as Mark.  So if functions are going to be created, then maybe they should be for the larger number of people who will use them.  Since only a small number of users can write in other languages, why not make Sesame functions with syntax and examples vs. functions that a larger group can really use?

I hope the tone of this reply does not come across as complaining.  I am just trying to throw some ideas on the table to be considered as priorities are set up.  Mark and Erika have been excellent in responding to requests and coming up with new features and tools.  See, you have spoiled us, and that is why I feel free to ask for more!  Because I know you will respond positively.  Thanks again for the help.

Looking forward to Version 2.