I would agree with Khalid's post. I have been doing this with Bridgview quite
easily.
However, if you need to port this data to machines that are not running Bridgview
software somne of the VIs that come with the Internet toolkit can come in
handy. Although I have found that at most times third party tools to port
data has been easier for me - perhaps because of familiarity or sometimes
"access to familiarity". If you need any help, please feel free to e-mail
me.
Sudhi
"Khalid Ansari" wrote:
>>Hello Wayne,>>You do not have to really know about these VIs. All you
have to do is to>run these "register VIs" once on your systems to register
the Remote Server>and Client. You'll then use the Network Tags to impelement
the Server/Clien
t>network. Also, you will not be using the TCP/IP VIs yourself.
All this>will be transparent to you.>>Regards,>>Khalid>>_________________________>"Wayne
Garret" wrote:>>>We have recently been developing
and Industrial Monitoring and Control>Application>using BridgeVIEW. The software
application consists of a SERVER>application>that is controlling and monitoring
the industrial application,>and a CLIENT>software application (in BridgeVIEW)
that has a subset of the>functionality>to control and monitor the HOST software
application from remote>terminals.>This means we are using the network tags
to synchronize the applications.>>I>learned of several VIs that are going
to be neede to make this application>fully>functinal. They are: rgstr RVBVC,
rgstr RVBVS, bvtcp client, & bvtcp>server.>>Does>anyone have any experience
using these VIs in a real-world application,>as>well as with a BridgeVIEW
Client/Server application.>>Thanks.