Hi Steeve,
DCOM should work since it makes reference to the server with the DLL. But do you know the real cause of the blocking problem. Is it that your server(s) (SQL and AOS) do not have enough resource to meet the load or is it some poor use of code? How many clients do you have connecting simultaneously (remember that 3-tier is scalable unlike 2-tier)? Do you thing of the fact that here is a possibility that your problem may not be solved going 2-tier?
Varden Morris
J. Wray & Nephew Ltd. - Group I.S.
Phone: (876) - 923 - 6141 Ext. 2226
Fax: (876) - 923 - 5372
Cell: (876) - 3833566
Email: [EMAIL PROTECTED]
Steeve Gilbert <[EMAIL PROTECTED]> wrote:
Hi Tom,
That would imply that fat people do more processing then thin people. Hmm� This isn't just politically incorrect, it's a non-sense. J Hey, it's Friday, gotta have some fun.
I know I do not need to modify my COM. But instead of only having to put it on the app server, I need to put it on every client workstation since the execution is done on the client machine. Later, if I modify my COM I'll have to change it on every workstation instead of only the app server. Maintenance goes up.
Steeve...
-----Message d'origine-----
De : Thomas Turney [mailto:[EMAIL PROTECTED]
Envoy� : 8 avril 2005 15:00
� : [email protected]
Objet : RE: [Axapta-Knowledge-Village] COM calling from Fat client
Steeve,
The Axapta installation courseware for 3.0 refers to two-tier, three-tier thin, and three-tier rich. I think they believe the term three-tier fat isn�t politically correct. I think the three-tier rich(fat) would not require any modifications to your COM process since it uses the AOS for application and a direct DB connection.
Tom T.
From: Steeve Gilbert [mailto:[EMAIL PROTECTED]
Sent: Friday, April 08, 2005 1:40 PM
To: [email protected]
Subject: RE : [Axapta-Knowledge-Village] COM calling from Fat client
We WILL move from <three-tier thin> to <three-their fat> soon enough. I wasn't really clear, we're not planning if you do the move, we're planning how we'll do it. That's why I'm concerned about my COM stop working since execution will be done client-side.
Three-tier rich? What is that?
Steeve...
-----Message d'origine-----
De : Thomas Turney [mailto:[EMAIL PROTECTED]
Envoy� : 8 avril 2005 12:31
� : [email protected]
Objet : RE: [Axapta-Knowledge-Village] COM calling from Fat client
Steeve,
Are you planning to go to two-tier vs. three-tier thin? If so have you tried three-tier rich?
Tom T.
From: Steeve Gilbert [mailto:[EMAIL PROTECTED]
Sent: Friday, April 08, 2005 10:13 AM
To: [email protected]
Subject: [Axapta-Knowledge-Village] COM calling from Fat client
Hi everyone,
We are currently in thin-client. We've developed an external COM that is called from a class in Axapta. This class's "call from" = "Server". So I installed the COM only on the Application server where the AOS and instance runs. That way, every Axapta client can use the functionality of the COM without having it installed on each workstation.
It's been a while we've been having blocking problem (SQL Process blocking each other) on our installation. After trying a couple of trick, we still get blocking and our MBS Partners suggested moving to FAT client. It seems there's no real reason behind this. What we've been told is that in thin client weird problems occurs that does not happen in FAT. Anyway, we're tired of blocking and we'll move to FAT.
Here's the problem. If I log in as FAT, my COM won't work since everything is executed on the client. Is there anyway to force execution on the server app even in FAT? Any other ideas? Going DCOM? I've never made any DCOM in VB.
Thanks for reading through.
Regards,
Steeve...
Sharing the knowledge on Axapta.
Sharing the knowledge on Axapta.
Sharing the knowledge on Axapta.
Sharing the knowledge on Axapta.
Sharing the knowledge on Axapta.
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
Sharing the knowledge on Axapta.
Yahoo! Groups Links
- To visit your group on the web, go to:
http://groups.yahoo.com/group/Axapta-Knowledge-Village/
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
