At the risk of sounding like a broken record, PTQ's in an Access database are the way to go with Knowledgesync also. KLF's use the linked table functionality and create a linked table for EVERY Sage table under the sun. If you add a UDF to a table, you have to refresh the link. With a PTQ, you do NOT. Setting up the linked tables takes a long time. Setting up PTQ tables do not. Once you have set up a master list of tables, you can move the Access DB to other customers. Modify the ODBC connection string. and you are good to go at the new client. Migrate to a new version of Sage, change the ODBC pathing in the PTQ and you are good to go with the new version.
An advantage of using PTQ's is that you can also use the same DB to power your Crystal reports - I have seen instances where the Crystal report runs 10X faster. These Crystal reports can added to the Customer Reports menu. The user does not know any different - except they run FASTER. Another advantage of use Access is that you can create select query tables, link Crystal to that table and possibly eliminate a subreport in Crystal.
I have to admit that I have only use the KS KLF functionality once. After a week of frustration, I went back to PTQ's. So perhaps if you get used to the pain of KLF's, you don't mind the pain. I couldn't suffer any longer...