🚀 go-pugleaf

Paul,

I looked into your suggestion.

Good news and bad news.

The good news: you were right, I had one .dll that was out of date.

The bad news: it didn't change a thing.

But, there is more good news... I got it to work.

In our office the *.exe is deployed into the same directory as the data
files on the server. This was done for convenience as the *.exe was
changing frequently (and still does change a fair bit now) so that
updating invidual client PCs was avoided. True (before you say it),
performance is not optimal, but it was well within acceptability for us.

I tried reinstalling the app on the server. Still had the problem. I
installed on my PC and it works fine (and, of course, a wee bit faster).
I guess I am going to have to bite the bullet and install in all client
PCs. I know that someone (I think Bowen Moursund or was it Romain
Streiff) posted a trick to get a app to update itself from a sourse on
the server. I will have to give that a try.

Thank-you very much for your help. If you can suggest an explanation as
to why things work, I would be interested. It must be something about
the network, but I am not sure what.


--
Geoff Wass
Kuala Lumpur, Malaysia


=============================================================
Please respond to a newsgroup posting by posting a reply (not e-mail).
In this way, all can help and all can learn!


=============================================================
Triumph is in the first syllable.