asiby wrote:
Wow
1. To save bandwidth a GUI will word well, and it gives me the idea of implementing AJAX into a2billing. This will help sending just relevant informations in some case.
I was able today to click the next button in the main A2Microsoft Gui and scroll through 220 records in just 5 seconds. Each record fully loaded far as I know. This just shows how much faster it really is.
asiby wrote:
2. In your GUI, you can lock the software if the reseller refuses to make the update with the new version. And you can make a backup of the previous version before upgrading.
Not a problem. The access program or gui can be told to check for a newer date in a mysql table on the a2b server (something you would enter) and if the date = later then what’s in the resellers Gui, a splash screen will pop up and keeps the focus with only 2 options, close or update. Closing will exit the access program. Making back up is not a problem as you wouldnt have reseller delete anything. They simply was forced to download a new file because their existing one was disabled.
asiby wrote:
3. In order to make the GUI more portable and cross-platform, some good programmer out there can create a GUI using GTK+ Runtime Environment, or Tcl, or simply using Open Office Database. (Just a suggestion)
Far as I know Open office can already read and link to .MDB files and MDB is the file type I am working with. The only thing is, I don’t think the access forms-gui is compactable with open office. The Excel and word replacement in open office should already be able to access the data linked tables in the Access MDB file for editable spread sheets or mail merge.
asiby wrote:
4. Most good and fast CRM are GUI based and not Web based (for obvious reasons). If you have manager to make a like between an organizer (like Outlook or Atc! for example) and a2billing, that will ease up a lot of thinks when it comes to handling a customer relation.
CRM (customer real-time management) This is where a2b really lacks and no matter how much work Areski does, even if he spent day and night for the rest of his life blistering his finger tips and wearing his keyboard lettering off he still wont be able to please everyone when it comes to CRM. Knowing this, the best thing he can do is make it more compatible to great CRM applications already on the market. And this is what I have done to some extent. I think mostly what is needed here is to change some of the data types in some of the fields in the a2b mysql database. Even for a2billing if I am not badly mistaken some of the data types being used now should be changed anyways to increase performance or save space. In other cases there will be a some loss of performance however the added benefit of users being able to use their own CRM application, far exceed this loss. Outlook, Atc, Act (Act maybe) , Excel, and Access are all either great customizable CRM applications or applications which can be used for buidling a CRM application and they all exchange data with each other with really no programming experience required. I very seldom use the web gui for A2b because I need to provide top quality customer service and web interface just doesn’t give me enough to work with.
If others have interest in what datatype to change I will post it in the correct part of the form.. I think things gone off topic here
(Correction) act used to share data back when i used it. I know i had both act and Access linked to same data files. but I just read now tha Atc is supose to share data a lot better then act. So who knows they might of change somehting .