VBA References missing

[SusanV]

Shared Access 2000 db app, works great for everyone until someone got a
replacement PC which was used by a past employee. Now on this one PC
functions are not running, compile errors, blah blah blah. Dug into
references, he's got a missing reference to Citrix ICA (turns out it was
installed incorrectly and never worked, reinstalling the ICA Client fixed
the problem)

My question is why does my app even HAVE a reference to the Citrix client?
Granted it's installed on nearly every PC in the company, but it has
absolutely nothing to do with my app. So why does it automatically include
itself? I have since removed it as a precaution so that the few people who
do not have it installed won't hit the wall if they need to use the app, but
I don't understand why it was there at all. Is it because it is installed on
my PC, so I need to be careful about installed stuff wherever I do dev in
order to not have this happen when distributing an app to a different
environment?

Thanks for any insight,

SusanV

 

[Paul Overway]

Either you or someone else set the reference...they don't just show up in
the list of their own accord. My guess is that someone was curious and
didn't know what they were doing, or was trying to do something they
shouldn't be doing. I'm not familiar with what methods and objects are
available in the Citrix client object, but someone could have been
attempting to use it for malicious purposes.

In any case, you should be distributing an MDE...that way the references
cannot be changed and you'd have more control over what modifications are
made to your app.

 

[SusanV]

Unfortunately, I work for a very small company, and since the group which
uses this app is very small (currently 5, the most would be 7 or 8) the
powers that be have decided that they don't want any kind of security or
passwords or splitting of the database. Not that they have any idea why
these things might be good or bad, mind you. Just because they decided.

<shrug>

It's a battle I continue to fight, eventually I hope to wear them down....
;-)

Thanks tons, appreciate your help!

SusanV

 

[Norman Yuan]

Splitting Access app to front/back end and making *.mde are so basic
approach to use Access in shared environment, to avoid a lot unnecessary
troubles. I cannot imagine some clients would insist "I prefer more trouble
than make thing work properly." It is we as developer to blame if client
thinks such basic thing will increase their running cost/inconvinience...

 

[SusanV]

Agreed, but it's their nickel

=D

Splitting Access app to front/back end and making *.mde are so basic
approach to use Access in shared environment, to avoid a lot unnecessary
troubles. I cannot imagine some clients would insist "I prefer more
trouble
than make thing work properly." It is we as developer to blame if client
thinks such basic thing will increase their running cost/inconvinience...