On 10 Jul 2009, at 9:31pm, Rick Ratchford wrote: > After examining the above, it appears that what this does is modify > the > table itself. So I suppose then that it is not possible to create a > recordset instead that meets what I'm trying to do. If this is the > case, > I'll have to make a copy of this table first as I don't want to > modify the > original.
I don't understand why people keep trying to do these things inside SQL when they're obviously ysing a programming language anyway. If the solution was entirely without a programming language there would be some point to it, but since you have your programming language, why not take advantage of it ? Keeping the previous value of a field in a variable does not take lots of programming ! Read the existing records from taxTable in date order. Compare the value of 'tax' in this record with the one you remember from the previous record. No need to write a new table. No need to write the directions to disk at all, since you apparently only need them for output. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
