You really should have just one customer table which contains all the
data required by both apps. That's the point of having a database - the
data is held only once - reduces maintenance and, since there's no
duplication, things can't get out of synch.
PT
Charlie Markwick wrote:
> Thanks for getting back to me. No these are separate applications each with
> their own version of Customers. When I originally started thinking about it
> I thought about creating a sort of mapping i.e.
>
> ZipCode in DB1 = PostCode in DB2
> or
> Address in DB1 = Address1,address2,addres3 in db2 etc
>
> But even if it was possible to do this how could I get one to update the
> other in real-time. It lost me at that point.
>
> Charlie
___________________________________________________________
To help you stay safe and secure online, we've developed the all new Yahoo!
Security Centre. http://uk.security.yahoo.com
------------------------ Yahoo! Groups Sponsor --------------------~-->
Most low income households are not online. Help bridge the digital divide today!
http://us.click.yahoo.com/cd_AJB/QnQLAA/TtwFAA/CefplB/TM
--------------------------------------------------------------------~->
The php_mysql group is dedicated to learn more about the PHP/MySQL web database
possibilities through group learning.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/php_mysql/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
