[quote="ajb":kbayfywy]If you can access DB, then we could pass the ID by database. But also we could pass this id by creating a simple txt file that will be served by http server to anyone - I don't think it's security issue, as it's only meaningless ID.
You should choose when to expose that ID. On contact view or at will with button. We can create a new button in the Action Bar for the contact - ID will be exported to DB/file on click. Then your app will pull this ID.
Last important thing is to solve user conflicts. I suppose you've got more than one active user. Every user could operate on his own EPESI and your app front ends, so I think that we should export contact ID per user. Is it possible to set user login in your app? Is frontend configurable per user?
EPESI module adds button. Button action will create file data/<some dir>/<recordset>/<user login> (e.g. data/some_dir/contact/admin - we could export most of the records in that way). Your app will pull this file with http://epesi.example.com/data/contact/admin.
To create this module you will need to know:
1. How to create module
2. Recordset Addons - especially addon_label static method, that will allow you to create button in action bar.
3. Create file with ID in certain directory.[/quote:kbayfywy]
Thanks this is very helpful.
1) I can easily access the MYSQL DB via ODBC from my application and each User has a separate Login for the Application and Database/Epesi so I can identify who they are. So I could easily have my application poll the file waiting for an entry to arrive. While it's polling, the user is busy using EPSI to create/find a contact.
2) I'd like the user to use EPESI to either create a new contact or find an existing contact, having done that, if they pressed a button to log it, that would work fine. If it was possible for that same button to minimise the EPESI browser window as well that would be good.
3) My application can then read back the relevant contact using the ID it's located in the table and display the Name etc as confirmation.
Thanks all sounds great, just need to work out how to make Epesi do it's bit!
For what it's worth, some simple method like this to enable a link to EPESI would probably be very useful for lots of people who have local MS-Access/VB apps or similar but who would like to use EPESI because the searching and other facilities in Epesi are really so good. I've got basic searching already in my local app, but it's no where near as good or flexible as the EPESI stuff, plus my local applications are not web enabled, hence the interest in EPESI. Lots of other people will be in a similar position, so I guess a simple interface like that would be very useful as standard in EPESI. Thanks again