Stephanie,

I was doing a search on vfp and queued components on UT today, and came across your message. I know your message was from July, and you may have already solved this problem by now, but in case you haven't, here is a suggestion.

While I have not yet worked with vfp 7 and queued components using a remote server/client, I started doing this with VB over this last weekend. I found that I was having the same problem in VB as you are having in VFP when calling a queued component on the server from a remote workstation.

I found the only way I could get it to work was to export an application proxy from the server, and install it on the Win2k pro box I wanted to execute it from.

You can do this by going into the component services console at the server, clicking on the application that the queued component is part of to expand it, then right click on the application and choose export. This will take you through a wizard that will allow you to create a microsoft installer package of that component as an application proxy.

Install the package on the client win2k box, and you should be able to execute it from the client box.

regards,

JE


>I created my first queued component with VFP 7 and it works when i call it locally directly on the server but if i try from a remote machine it doen't work.
>
>When i try this on on local server it works:
>

>lobj = GetObject("queue:/new:MyServer.MyClass")
>

>From a remote workstation this works:
>

>lobj = CreateObject("{8E773F60-239D-4F93-8051-1186A07D89AF}", MyServer)
>

>But it not using the queue moniker. When i try this:
>

>lo = GetObject("queue:/new FormatName=DIRECT=TCP:192.168.1.101\{8E773F60-239D-4F93-8051-1186A07D89AF}")
>

>I get an error saying my component is not marked as queued BUT IT IS !! How come the first example works ?
>I know i am doing someting wrong but what ?
>
>Thanks.