Hi Gjergj

Exactly on that integration idea I will work. Next 10 day's I have some
other tasks on my desktop, afterwards we can think about real smart and
usable interface for that work. As I mentioned for some months, I do not
agree that webERP and care2x should merge or even "smelt together". When we
following so called SOA ideas we and webERP has quite better opportunities.
Let the accounting work for erp developers. 

Robert


--------------------------------------------
MEROTECH IT Engineering

Robert Meggle
Hohnerstrasse 6
89079 Ulm

Germany

Tel: +49(0)7 31- 1 75 97- 27
Fax: +49(0)7 31- 1 75 97- 25
mailto:[EMAIL PROTECTED]


> -----Ursprüngliche Nachricht-----
> Von: [EMAIL PROTECTED] [mailto:care2002-
> [EMAIL PROTECTED] Im Auftrag von Gjergj Sheldija
> Gesendet: Dienstag, 16. Oktober 2007 23:07
> An: care2002-developers@lists.sourceforge.net
> Betreff: Re: [Care2002-developers] Integrating the DB's
> 
> hio tim,
> 
> yes, absolutely the same thing :)
> 
> but, since care2x is going to stop at this version & we will begin the
> work on care3g,
> any - even minimal - integration of care2x & weberp is wellcome :)
> 
> on care3g we will be using somethink more _cool_ such as xmlrpc
> (soa,webservice,...)
> and make a proper analysis on how things should work. the ideal would be
> something very loosy...anyhow 'till then anything is wellcomed :)
> 
> regards
> gjergji
> 
> 
> Tim Schofield wrote:
> > Hi gjergji,
> >
> > Yes I agree. A proper plan on is what is called for. What I was trying
> > to say - possibly badly - was that any integration should be as simple
> > as possible, and have minimal changes to both projects, thereby making
> > updates so much easier.
> >
> > i think we are both saying the same thing here.
> >
> > Thanks
> > Tim
> >
> >
> > On 16/10/2007, Gjergj Sheldija <[EMAIL PROTECTED]> wrote:
> >
> >> hi,
> >>
> >> there are obviously pro's and con's on integrating the db,
> >> allthought we have to ask a question, for what in care2x
> >> are we going to use weberp ?
> >> i might propose
> >> - med depot
> >> - patient billing  ( for inpatient / outpatient ) :
> >>     - days in hospital
> >>     - pharmacy
> >>     - lab
> >>     - blood center
> >>     - radiology
> >>     - service type
> >>     - insurance type
> >>
> >> and other things such as payroll & other accountability stuff for the
> >> hospital...
> >> so, if you see it this way, you don't even need common login & common
> >> sessions,
> >> except maybe for some cases where nursing is also involved with
> >> accounting, wich can
> >> simply be resolved in to logins, one on care2x, the other on web erp...
> >>
> >> anyway it's just how one might look at the problem.
> >>
> >> regards
> >> gjergji
> >>
> >>
> >> Tim Schofield wrote:
> >>
> >>> Why integrate the databases? Surely this is only making things more
> >>> complicated than it needs to be, and making maintenance a nightmare.
> >>> Both databases can be accessed from within the same scripts.
> >>>
> >>> All you need to worry about is when you need a query that accesses
> >>> both databases - I'm not an expert on Care2x but I know weberp pretty
> >>> well, and I would be surprised if you need to do this often, if at
> >>> all.
> >>>
> >>> More important is a common login, and shared session variables, and I
> >>> would have thought this was a better area to put our efforts into.
> >>>
> >>> Thanks
> >>> Tim
> >>>
> >>> ----------------------------------------------------------------------
> ---
> >>> This SF.net email is sponsored by: Splunk Inc.
> >>> Still grepping through log files to find problems?  Stop.
> >>> Now Search log events and configuration files using AJAX and a
> browser.
> >>> Download your FREE copy of Splunk now >> http://get.splunk.com/
> >>> _______________________________________________
> >>> Care2002-developers mailing list
> >>> Care2002-developers@lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/care2002-developers
> >>>
> >>>
> >>>
> >> -----------------------------------------------------------------------
> --
> >> This SF.net email is sponsored by: Splunk Inc.
> >> Still grepping through log files to find problems?  Stop.
> >> Now Search log events and configuration files using AJAX and a browser.
> >> Download your FREE copy of Splunk now >> http://get.splunk.com/
> >> _______________________________________________
> >> Care2002-developers mailing list
> >> Care2002-developers@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/care2002-developers
> >>
> >>
> >
> > ------------------------------------------------------------------------
> -
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > Care2002-developers mailing list
> > Care2002-developers@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/care2002-developers
> >
> >
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Care2002-developers mailing list
> Care2002-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/care2002-developers


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Care2002-developers mailing list
Care2002-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/care2002-developers

Reply via email to