I have been a long time subscriber of Quick Answer and learned a lot from the insightful articles that it came out with month after month.  I have incorporated a lot of different ideas into my system from this monthly. I look forward to have Sesame Inside every month. It is a great value for the the bucks and I recommend everyone here to subscribe to "Inside Sesame" if you as a non-programmer wish to make a custom application and grow with it. It has been an indispensable element in my learning and growing process as far as database applications are concerned.

Okay, here's, a hint -- and the crux of the procedure. A loop where vLoop is the counter variable:

@FormFieldValue("LineItem", "StockNo", vLoop)

Quote:

I don't mind paying the freight for a complete product. But I think that if the original intent was to produce a product that replaced a "workhorse" in the field, then it would make sense to be able to deliver a product that meets or beats the original feature for feature.

In the main I believe that Sesame meets this goal with the exception of a few items. Reports I would like to see become more polished, including a utility for making labels. I would like to be able to do this from the database and not have to port this through Word or Wordperfect.

The import and export features are present but they seem minimal, I would like to see Sesame offer at least the same capability with reference to ASCII files as Q&A did.

My earlier comment about being able to "tell the time and not having to build the watch" applies in these circumstances. I don't have the luxury of having time to program in Sbasic and debug  all of these features which I'm sure can be done. I just need to get my work done as efficiently as I can because of work imposed deadlines.

As Hammer says, Sesame is actually pretty rich in import/export features. The main shortfalls are dBase import/export, and Fixed ASCII. The one we hear about most is Fixed ASCII import.

Sesame CAN import fixed ASCII. Just not directly. You need to use programming. I described the procedure in the January issue of INSIDE SESAME.  Sure it might take you half an hour to set it up, but the effort is little different to what Q&A required. And, like Q&A, once set up it can be stored (as a saved mass update) for instant re-use.

As far as I can see, export is good with all different choices. Import, other than hierchical import, it is not really upto par. You do not have even choice to have different delimiters. I had to first import a file in Q&A and make it compatible, so Sesame can import and that says a lot about Sesame Import. I would imagine that one would make certain that import is a quite versatile so as to make data tranfer easier for the people who wish to migrate from other competitive products.

This one could be long winded  and probably in the wrong section but I'm looking for suggestions on the best way to bring sales tax into our system.

After reading the March issue on the Invoice System, I decided to implement some of Tom's ideas into our point of sales system, which has brought about some other problems.
In our point of sale invoice system (which is not fully tested until we recieve the 1.0.2 upgrade for subform calculations) I have been working on bringing in the new State Sales Tax tables which went into effect the first of the year but we have till May to have it fully operational before we are in non-compliance.

Under this system we have to collect sales tax at the point of delivery which apparently is to work off the 5 digit zip code with the plus 4 to obtain the tax rate for that paticular address.
As this system now gives us over 872 tax rates for the state the question now comes to the best way to incorporate this into our invoice form.
With one or two tax rates it was easier to add it as a line item in the subform but with 872+ rates I placed a check box for taxable, an LE for tax after the subtotal and planned on doing a xlookup to return the tax rate then do the calculations.
As the State Dept of Revenue now tells us the downloadable date base will not be available until May and they don't know what format it will be in yet  but they tell us there is a data base on the Dept of Revenue's Website you can input the address to get the tax rate, or input the address invoice amount and it will return the tax amount.
I then get to thinking about the size of this database for these new tax codes; as it is to work off the zip +4 then every address for the state will be listed in it which will be around 3 to 5 million or better, so now what.

Is it possible to do a lookup to the website database in this scenario?
How taxing (excuse the pun) will this db and lookup be to Sesame if it were download into Sesame for use?

I also understand there is 13 states that have now introduced this tax system with more to follow, so if theres other Sesame users fighting this same problem I would like to hear how your handling it.
Or if you undeclared guru's of Sesame have any thoughts as to the best way to handle this to keep the burden to the system at a minimum, would love to hear it.

Ok, everyone reading this is now asking why is the state doing that, well it appears our governor thinks she going to start collecting sales tax from internet sales and this is stage one being implemented, talk about re-inventing the wheel

Hi Bob, http://www.ksrevenue.org/streamline.htm
Middle of the page with hightlight arrow is one db then if you go down the page to "Sales and Use Tax Address Tax Rate Locator" you will find db's for address and zip +4 lookups, these I found the easier to use.

Either way this one's a mess  
thanks becky

My mistake Bob, both links go to the same page where the address and zip+4 db lookup's are