Re: VB6 App On MS Server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance


"Jeremiah D. Seitz" <jseitz@xxxxxxxxxxxxxxxxx> wrote in message
news:sitju3tdikp6j1jk99blh86td82g7k3a0a@xxxxxxxxxx
On Tue, 25 Mar 2008 22:55:03 -0500, "Ralph"
<nt_consulting64@xxxxxxxxx> wrote:

Whenever, there is an issue with something that works in one environment,
but not in another - it's because you are dealing with different
critters.
The reason I asked is that there are known issues with the install of DAO
on
Server 2003+. It is quite possible you are using a translator on the
server.
(see previous article) That would certainly cause performance issues.
And -
this is pure guesswork on my part - but there are also locking behavior
difference between versions 3.5 and 3.6 that might lead to a deadlock if
using 3.6. ????

Ralph,

Would it be possible for the OP to run the *source* from the
server? (VB6 /r project) It's an idea I've never tested, but from what
I gathered, the OP has access to the server, and might be able to
trace any errors with a judicious use of Stop and F8.


The /r option would compile the project and then run it, so it would be no
different than simply runing the compiled exe on the workstation. If the OP
has access to the Server then he could just as easily run the project in the
IDE.

I realized now that my suggestion of DAO versions is a little silly because
it sounds like the application is being run in the Workstation Address Space
anyway. The only difference is getting to the Database file across a wire
compared to accessing it locally. (Overly thunk it. <g>)

Its all guesswork until we at least know exactly *where* the app is hanging.

-ralph


.

Quantcast