project in two-tier mode, ideally while in the dat company (since it doesn't
cache). At a push, you could import into one AOS, and force a cache refresh
on the others (Tools->Dev Tools->App Objects->Refresh AOD), but we found
that to be pretty unreliable.
The fun part is convincing the business that you need to bring the system
down to do imports ;)
Regards,
Matt Benic
Axapta Developer
UTi Sun Couriers Division
"The universal aptitude for ineptitude
makes any human accomplishment an incredible miracle."
- Col. John P. Stapp
-----Original Message-----
From: axaptaci [mailto:[EMAIL PROTECTED]
Sent: 16 September 2004 02:08 PM
To: [EMAIL PROTECTED]
Subject: [development-axapta] Multiple AOS with multiple Application
Directories
Hi,
I have read some mails about Axapta that we must use One DB and One
Application folder. But our customer has 4 branches. I made this
desired configuration with 4 AOSs but only one of them can work,
others have some event messages about out of license (I found that
the real reason is that one AOS exclusively locks the application and
the others cannot get connected).
When we configured the system with multiple AOSs and multiple
Applications using the same DB, it works... But now we have the
syncronisation problem...
Problem is, when we import a projec to one AOS how can we import to
other AOSs automatically?
Best regards,
meyaki
Yahoo! Groups Links
| Yahoo! Groups Sponsor | |
|
|
Yahoo! Groups Links
- To visit your group on the web, go to:
http://groups.yahoo.com/group/development-axapta/
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
