I have found myself somewhat trapped in a project where the software
being used is essentially set in stone, and its limitations are
strangling progress. It is a client-side app written in VB with an
Access backend, and it has no reasonable data migration/synchronization
ability. It was
John McCawley wrote:
I have found myself somewhat trapped in a project where the software
being used is essentially set in stone, and its limitations are
strangling progress. It is a client-side app written in VB with an
Access backend, and it has no reasonable data
migration/synchronization
I'm not really sure what switching development platforms for the tool
would buy me. Are you saying that the wire-protocol used by vb.net and
C# etc. is substantially faster than what is available in VB? Regarding
ASP.net, I don't really see how a web app would help here, as it has to
run on
On 11/22/06, John McCawley [EMAIL PROTECTED] wrote:
I'm not really sure what switching development platforms for the tool
would buy me. Are you saying that the wire-protocol used by vb.net and
C# etc. is substantially faster than what is available in VB? Regarding
no, the wire protocols are
John McCawley wrote:
I'm not really sure what switching development platforms for the tool
would buy me. Are you saying that the wire-protocol used by vb.net
and C# etc. is substantially faster than what is available in VB?
Regarding ASP.net, I don't really see how a web app would help here,
I think I may not have described my problem clearly enough...I *already*
have a server-side app written in PHP with a Postgres backend...This is
the ultimate destination of the data. The problem is that I am being
forced by my client to deploy a 3rd party app on all of my field guys'
Merlin Moncure wrote:
no, the wire protocols are the same (dictated by the server). also,
c# and vb.net are almost functionally the same language.
Hi,
From experience NPGSQL seems faster than ODBC, though they have the
same wire protocol. Must have something to do with the overhead of
John McCawley wrote:
I think I may not have described my problem clearly enough...I
*already* have a server-side app written in PHP with a Postgres
backend...This is the ultimate destination of the data. The problem
is that I am being forced by my client to deploy a 3rd party app on
all of
John McCawley wrote:
I think I may not have described my problem clearly enough...I
*already* have a server-side app written in PHP with a Postgres
backend...This is the ultimate destination of the data. The problem
is that I am being forced by my client to deploy a 3rd party app on
all
