FOr each frmTest in FOrms construct curiosity

[Martin Newman]

Have a set of 3 pretty big adp's (all hitting the same SQL DB) I have been
developing over the last year. Currently being developed using Ac XP and
deployed as an XP runtime with the adp in A2000 format. Been working as
expected for ages - I bring out upgrades regualrly and all hunky dory.

There is a routinew which all three adp's use (but spereatley in each adp -
must sort that sometime soon) that uses the construst

FOr each frmTest in Forms

have started failing for Type Mismatch when delpoyed using teh runtime but
fine when using full Access - works on the machines to which the adp's have
been delpoyed if you use A2003 (which happens to be running on those
machines) ratyher than the A XP runtime.

Replacing the construct with

for i = 0 to Forms.count - 1

solves the problem. This applies to each of the adp's independantly

Eh?? WHat's up??

Martin

 

[Nick Coe \(UK\)]

Interesting.

Double check your declaration of frmTest is right type of
object. Double check references on client machines.
Jetcomp.exe your project before running on client machines.

Search the MSKB for the AccXP /runtime switch - I've a
feeling it messes with the registry rather than being a
switch you specify at runtime to msaccess.exe.

Can't think of any other suggestions - Real odd one there
mate...

 

[david epsom dot com dot au]

I wonder what other access apps are running on those PC's?
I'm curious to see if the behaviour is different if you have
A2003 or a particular A2003 application open already when
you open the XP runtime.

(david)