Calling another program

[John Wright]

I have a central program I am starting to develop that will track processing
deviations. This program is VB 2008 and needs to be called from VB 2005
programs and VB2008 programs (we have some VB 6 programs as well but I these
are getting phased out). I need to call this program, pass the logged in
user name, and fill in essential data from the calling program into the called
program. I don't really want to create a deviation form for all the existing
programs, I would just like to launch this program and fill in the corresponding
data. The following will be a typical scenerio for the program, I have indicated
what I have done with (DONE) at the end of each line

The operator is using their program to enter production data. The program
is written in VB.NET 2005.(DONE)
During processing a processing deviation occurs requiring them to create
a deviation notice (EPN).(DONE)
From the program the user would click a button or a menu item called EPN(DONE)
The program would call the EPN program, and when it is loaded, fill in the
required data
The user would then enter the remaining data, add some attachements if necessary
and start a deviation process.
The EPN program would place the material in deviation status (DONE)

As you can see I need some suggestions on how to incorporate the EPN program
into existing .NET programs with little interference and updating.

Any suggestions, right now I am open to anything? I have looked a using
web services, command line launching, embedding the EPN program in all existing
programs.

John

[rowe_newsgroups]

Re: Calling another program

On Nov 7, 12:51 pm, John Wright <riley_wrig...@ hotmail.comwrot e:

I have a central program I am starting to develop that will track processing
deviations.  This program is VB 2008 and needs to be called from VB 2005
programs and VB2008 programs (we have some VB 6 programs as well but I these
are getting phased out).  I need to call this program, pass the logged in
user name, and fill in essential data from the calling program into the called
program.  I don't really want to create a deviation form for all the existing
programs, I would just like to launch this program and fill in the corresponding
data.  The following will be a typical scenerio for the program, I haveindicated
what I have done with (DONE) at the end of each line
>
The operator is using their program to enter production data.  The program
is written in VB.NET 2005.(DONE)
During processing a processing deviation occurs requiring them to create
a deviation notice (EPN).(DONE)
From the program the user would click a button or a menu item called EPN(DONE)
The program would call the EPN program, and when it is loaded, fill in the
required data
The user would then enter the remaining data, add some attachements if necessary
and start a deviation process.
The EPN program would place the material in deviation status (DONE)
>
As you can see I need some suggestions on how to incorporate the EPN program
into existing .NET programs with little interference and updating.
>
Any suggestions, right now I am open to anything?  I have looked a using
web services, command line launching, embedding the EPN program in all existing
programs.
>
John

Maybe I missed the explanation when I skimmed over your post, but why
couldn't this "central program" just be a dll (COM compliant for VB6)
that's referenced by the other applications?

Also, you say what you've looked at, but since you posted the question
I'm guessing you deemed them sub par. So would you mind explaining why
you don't like webservices, command line args, etc?

Thanks,

Seth Rowe [MVP]

http://sethrowe.blogspot.com/

[John Wright]

Re: Calling another program

Hello rowe_newsgroups ,

On Nov 7, 12:51 pm, John Wright <riley_wrig...@ hotmail.comwrot e:
>

>I have a central program I am starting to develop that will track
>processing
>deviations. This program is VB 2008 and needs to be called from VB
>2005
>programs and VB2008 programs (we have some VB 6 programs as well but
>I these
>are getting phased out). I need to call this program, pass the
>logged in
>user name, and fill in essential data from the calling program into
>the called
>program. I don't really want to create a deviation form for all the
>existing
>programs, I would just like to launch this program and fill in the
>correspondin g
>data. The following will be a typical scenerio for the program, I
>have indicated
>what I have done with (DONE) at the end of each line
>The operator is using their program to enter production data. The
>program
>is written in VB.NET 2005.(DONE)
>During processing a processing deviation occurs requiring them to
>create
>a deviation notice (EPN).(DONE)
>From the program the user would click a button or a menu item called
>EPN(DONE)
>The program would call the EPN program, and when it is loaded, fill
>in the
>required data
>The user would then enter the remaining data, add some attachements
>if necessary
>and start a deviation process.
>The EPN program would place the material in deviation status (DONE)
>As you can see I need some suggestions on how to incorporate the EPN
>program into existing .NET programs with little interference and
>updating.
>>
>Any suggestions, right now I am open to anything? I have looked a
>using
>web services, command line launching, embedding the EPN program in
>all existing
>programs.
>John
>>

Maybe I missed the explanation when I skimmed over your post, but why
couldn't this "central program" just be a dll (COM compliant for VB6)
that's referenced by the other applications?
>
Also, you say what you've looked at, but since you posted the question
I'm guessing you deemed them sub par. So would you mind explaining why
you don't like webservices, command line args, etc?
>
Thanks,
>
Seth Rowe [MVP]
http://sethrowe.blogspot.com/

COM is right out. It is not a supported technology here. Command line is
an option we will pursue with the VB 6 programs. I know you can call Webservices
through VB but it was clumbsy and the programmers here could not support
it. As for the .NET I am creating a user control that will interface via
Web services to the EPN engine so they can drop the control in a program
and use it. I use web services and will use that in the .NET. Command line
args are okay, but it is just another point of failure should the command
line fail (rare I know, but it can happen). So for the VB 6 programs, it
will be a command line launch, for the .NET apps it will be a user control
and web services.

John