OT: Confirm Citrix Session PC-Independent?

[PeteCresswell]

I just posted this in the Citrix group, but I'm thinking (maybe more
accruately,
grasping at straws) that maybe, just *maybe* there's some MS Access-
specific
twist to this.
------------------------------------------------------------------------------------------------------------------

We're in the second day of a two-day nightmare. The second night,
actually.....

An MS Access application that's been working pretty well in a Citrix
environment has started getting flaky post-changing Citrix servers.
("Citrix Server" being a logical PC within a VMWare scheme on some
sort of industial-strength computer that I know nothing about).

What's weird is that the problem application works a-ok on my
developer PC and the PC next to it: both minitowers.

But the problem application exhibits it's bad behavior on a laptop -
probably every laptop that uses it if the logs are tb believed, but
definitely on this one laptop as actually witnessed.

All three situations are replicable - having been done six times each
absolute minimum.

We've also tried with my own userid (the developer), a Windows Server
admin's ID, and one of the application user's IDs. No correlation
found with ID, only with the box.

What I'm trying to tell everybody concerned is that to the API calls
and MS Access VBA code within the problem application it doesn't make
any difference whatsover what the user's PC is.

i.e. There is nothing, absolutely *NOTHING* in the environment seen by
the MS Access app running in a user session on the Citrix server that
is influenced by the PC that the client is running on. Nothing,
nada, bupkis, zilch.

I really don't know enough to make such an assertion - but it seems
logical and I've been making it - rather loudly at times.

Yet we've got this difference in behavior between two minitowers and
the laptop.

So, how about it? Am I lying to these guys?

 

[David W. Fenton]

:

Yet we've got this difference in behavior between two minitowers
and the laptop.

Different versions of the RDP client?

 

[Tony Toews [MVP]]

An MS Access application that's been working pretty well in a Citrix
environment has started getting flaky post-changing Citrix servers.
("Citrix Server" being a logical PC within a VMWare scheme on some
sort of industial-strength computer that I know nothing about).

What's weird is that the problem application works a-ok on my
developer PC and the PC next to it: both minitowers.

But what is the problem?

Are you folks on the same version of Access and Service Pack? What
about msjet40.dll version?

i.e. There is nothing, absolutely *NOTHING* in the environment seen by
the MS Access app running in a user session on the Citrix server that
is influenced by the PC that the client is running on. Nothing,
nada, bupkis, zilch.

I haven't seen anything but that doesn't mean that something weird
with an API call couldn't happen.

Tony

 

[PeteCresswell]

But what is the problem?

I don't know the root problem - only that a couple of the form's
subroutines are trapping out.

The rules for a subform with no records seem to change. On the
"good" PCs,
no error is thrown if there are none of a certain record. On the
problem PCs,
we are throwing error 2467 (Object closed or does not exist).

Are you folks on the same version of Access and Service Pack?  What
about msjet40.dll version?

Access/SP, yes.

Had not thought to check MSJET40.DLL. Will do immediately -
especially since the 2467 seems to smell of JET....

I haven't seen anything but that doesn't mean that something weird
with an API call couldn't happen.

Somewhere around 2 this morning, it dawned on me that at the very
least, the graphics driver must be a player, since the client (or
*somebody*) resizes the application's window to fit whatever PC the
Citrix sesh is on.

Gonna check that MSJJET level right now.

 

[PeteCresswell]

Are you folks on the same version of Access and Service Pack?  What
about msjet40.dll version?

Funny thing: in the production and QA Citrix environments, I can see
MSJET
in Help|About Microsoft Access|SystemInfo|Software Environment|Loaded
Modules and the versions are the same: 4.00.9505.0

But on my PC, MSJET does not even show in abovementioned list.

Clearly something's there.... or I wouldn't be running.... and I don't
see any "View" or "Select" option that might be filtering out MSJET.

Any thoughts?

 

[Tony Toews [MVP]]

I don't know the root problem - only that a couple of the form's
subroutines are trapping out.

The rules for a subform with no records seem to change. On the
"good" PCs,
no error is thrown if there are none of a certain record. On the
problem PCs,
we are throwing error 2467 (Object closed or does not exist).

That must happen in code then.

Access/SP, yes.

Had not thought to check MSJET40.DLL. Will do immediately -
especially since the 2467 seems to smell of JET....

They might be at different versions of Jet as the version number can
differ depending on the OS. Check the KBs mentioning that Jet
version to see if they are really the same.

Tony

 

[Tony Toews [MVP]]

Funny thing: in the production and QA Citrix environments, I can see
MSJET
in Help|About Microsoft Access|SystemInfo|Software Environment|Loaded
Modules and the versions are the same: 4.00.9505.0

But on my PC, MSJET does not even show in abovementioned list.

Clearly something's there.... or I wouldn't be running.... and I don't
see any "View" or "Select" option that might be filtering out MSJET.

Any thoughts?

Not a clue. I've never looked at that. I always just go find the
file. Or the following standard blurb.

What I've done is use the various API calls available and am checking
the version number and date/time of a crucial dll, msjetxx.dll, to
ensure it matches what I have on my system. See the Verify
Appropriate Jet Service Pack is installed page at my website for more
details including sample code:
www.granite.ab.ca\access\verifyjetsp.htm

Tony

 

[David W. Fenton]

m:

But on my PC, MSJET does not even show in abovementioned list.

Clearly something's there.... or I wouldn't be running.... and I
don't see any "View" or "Select" option that might be filtering
out MSJET.

The version of Jet on the client PC can't have any effect on the
remote desktop session. I'd say the version of the RDP client (or
whatever Citrix uses) is the place to start, and your mention of
video drivers also seems a good thing to look at.