Probably NOT!!. All depends on how the program works right now. Some
possibilities:

- Maybe the 6% is locked into code, and must be changed there. Do you have
the original PAL (*.SC) files? BUT, you may still not be able to change a 6
to a 7 - what would happen then, for example, if you want to re-print a
transaction from a few months back, when the rate WAS 6?? Or how are your
historical reports impacted if you change a 6 to a 7 in mid-flight?

- Maybe you currently select a tax "code" (say code X), which goes into
some Tax-Code file, and there it establishes that code X means "6%". In that
case, you probably should still NOT change Code-X to 7% - because all your
existing data "thinks" (?) that Code-X means 6%. Maybe you should create a
new entry, Code-Y, set it to 7%, and use that new code going forward.
Maybe...

- If the actual rate is held on Product records - which would be
unlikely - then you could change these with a "Query", but again, this might
impact other sub-systems.

As Steve and Larry have said, we know far too little to be able to help
definitively. I think someone will need to delve into the entire app, and
see how the tax is handled - EVERYWHERE in the system. The 7% mod might then
be simple or quite tricky...

- Mike

R wrote:

Let's say you called up a masonry trade association, told them you had a
brick house and wanted to know where the coat closet is. They could guess
based on typical designs they'd seen in the past and tell you it's probably
close to the front door. They might be right, or you might want up putting
your coats in the powder room toilet. :-)

--
Larry DiGiovanni
Digico, Inc.
IT Consulting and Staffing Solutions
www.digicoinc.com
Check out www.thedbcommunity.com for Paradox resources.