I have several ecommerce sites and every day their order files are downloaded into an Access system and from there a whole host of stuff is done including sending a file to the fulfilment house, creation of returns/receipt of returns, delivery failure logs etc. etc.
Basically, due to remote working requirements I want to move this access database into a more user-friendly online environment and am looking at your product to do this. All the sites are php/mysql so it's a platform I'm comfortable with.
Anyway onto a few questions after playing with the trial verion.
- It seems that for each project you can only have 1 master-details set up. Would this mean I would need 1 project (and therefore a set of directories for each project on my web server) for each main area of operations.
E.g. opening/amending/viewing order details would use the master table ORDERS but would have detail pages (for look up descs etc.) of PRODUCTS, WEBSITE, KIT_PRODUCTS etc. etc.
Another "set" or project would be the returns/RMA's. So I would have the main table RMA_CREDIT as the master and then I would have as detail tables ORDERS, PRODUCTS, RMA_STATUS, CREDIT_STATUS tables for customer details, product descriptions, rma status descs and credit status descs respectively.
Would this be another project and as such require a different directory on the server.
So, for example, I would have www.mydomain.com/backoffice/orders and www.mydomain/backoffice/returns and www.mydomain/backoffice/purchasing etc. etc.
Hope this makes sense! It kinda does to me - trying to build 1 project that somehow does the whole back office thing sounds scary but breaking it down into smaller project where a specific process is dealt with sounds more like it. Is this how it was designed to work?
- Security/Access
I can see that I can say which tables and which columns can be added/amended/deleted etc but can I set access to tables via users? Basically there will be tables on there I want to maintain, i.e. static data like return reason codes and their descriptions, that I don't want everyone having access to. It would be good to say which users can have access to what tables and what they can do against each table (add/edit/delete etc.) - is this possible? The "groups" functionality seems to indicate that it is.
- Choosing fields and other stuff
Once you have chosen your tables (lets stick with my example of a RETURNS table as the master data which then has RETURN_REASON and CREDIT_REASON for lookup of descriptions for example) is it possible to decide what you are going to show, in what order, whether you can delete/add/view/search on ALL tables or only just the master one?
- Fields orders & Totals
There are several tabs (List/Edit/Add/View/Search/Export etc. etc.) - is there any way once you have set it up for list view there is a copy across the order to the rest of them?
How does the Totals Type thing work?
- MySQL question - can it deal with VIEWS or TRIGGERS yet? Do you know? It would be good once I upload orders into the ORDERS table in my database for this to automatically create entries in the contact-log table for example. If TRIGGERS can't be done yet what about scripts running on a scheduler - can this be done in MYSQL?
That;s about it for now.
