The trans.log is made to not be opened and altered. That would be an enormous security risk if you could open a trans.log from a previous day and remove sales. That would equate to a license to steal from owners or franchisors.
There is a tran.log tool however it is not available to end users for scurity reasons.
Can you tell me more about this tool and who it is available to? We are writing an application that integrates with ALOHA. It needs to be able to read and write to the tran.log.
You will have to contact Radiant and they will determine this. There are others out there who have done this like LoneTree Technologies. Check out their website and see if they haven't already done something similar to what you are trying to do.
I would love to get my hands on the trans.log tool. I am very interested in writing an application that integrates with Aloha and would also need to read from the trans.log.
Just so you know, lawlegacy, that Radiant will only give their SDK to "approved" vendors. This is extremely difficult to get even for established development houses, so the odds that you will get this are precisely zero.
You may want to explore the possiblility of editing 'grind' files. Grind files are multiple dbf files that are created to feed data into the reports so that you can view sales data, etc. You shouldn't really edit these files, as they can easily be re-written by the application, but to read data and import it into another database, for example, can be useful and is a fairly common practice.
But to write to a translog is a 'no-no'. The IRS will staple you to a cactus in Nevada, and Radiant will lose all certifications and reputation (what's left of it).
Also, may I ask what your role is? Are you a restaurant owner, a developer, or ????
All I can really tell is that you somehow got your hands on a POS system.
It would help me to address some of these issues differently.
If only the log viewer worked as good as advertised. I can only use it on several versions of Aloha. Has anyone else been able to use it effectively without it crashing to the desktop.
No, and No. You cannot input into a translog, except by using the POS system, or COM hooks, which you will not get from Radiant. You are not allowed to read a trans.log Only Radiant Technicians are allowed. (people that claim to have it, acquired it subvertly) It is encrypted for a reason.
Again, MAJOR security issue.
In other words, give up on this. Use a third party who has successfully integrated with Aloha before and has a currently working product.
OR... write your own POS software. Or.. buy another POS package that does what you want it to do.
I am struggling with Radiant to give an SDK to a MAJOR software house and I am a HUGE customer of Radiant and they still won't sell it to them without a LENGTHY approval process.
what would you need to read from the trans.log that is not currently available in the GRIND files?
If you can be somewhat specific you may get one the of various members to advise you.
As for writing to the trans.log; unless you have an incredibly fantastic concept that would be equally fantastic for a large majority of end users...forget it, that dog won't hunt.
Since its inception in 1994, Aloha (Ibertech) ain't handing anybody the keys to the translog.
It took them 5 years to release the Audit tool BEFORE they add it to the AlohaMgr.
Again, be specific and you may get some results.
You can interface with Aloha thru the com interface built into the software. I have used it was setting up an online order system. In that case I used an interface produced by "Decision Tree" that communicated with Aloha. Our interface took web orders, converted that order to XML and sent them to the Decision Tree software. You might try takling to them about it?
The com interface can do other things such as act as an "Aloha print server" to send print jobs...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.