References in VBA in Runtime distribution to non-Access machine fa

[Juan Carlos]

I have an Access 2003 app that uses the string function Right. Even in my
original program database, it flagged this as unknown until I went into
references and picked (randomly, since they are all named the same) one of
the many Visual Basic for Applications references. It didn't seem to matter
which one I picked, it worked (even though I already had VBA selected as
reference by default). Interestingly enough, this did not create a second VBA
reference. References did not appear to change, only the Right function is
now recognized.

However, now that I am distributing the app via runtime, it fails. The
database works correctly in runtime mode on my machine but fales on the
target machines. I finally installed access 2003 on one of the target
machines, and found, even though the VBA reference is checked, the Right
function fails again. I assume this is the cause of my problem. This is
difficult to tell for sure since the AccessRT error reporting is pretty thin.

So, assuming this is my problem, how do I fix this for my customers. I
supposed I can write my own Right function, but that seems dumb. Any other
suggestions?

Thanks,
Juan Carlos