Re: Access 2000 subform: problem accessing a property or method of the OLE Object

Hello Stefan,

Yes, I always make my own menu/toolbars.
It's pretty easy and you can give the users exactly what they need (and not to much).

Good luck!
Bas

Hi bas,

Thanks for the input. Some advanced users will start to use the old
application with the /runtime - switch to see, if they're missing some
functionality.

Did you create own toolbars for your customers?

Stefan

bas schrieb:

Hello Stefan,

I'm having a customer working with Access 2003 runtime and ADP's. Not
much trouble so far.

You can test for yourself by starting access with the /runtime
switch, ie:

C:\PROGRA~1\MICROS~3\OFFICE11\MSACCESS.EXE "F:\Data\Your-PROG.adp"
/runtime

Regards,
Bas
Hi Sylvain!

Thank you very much for your response. I already thought that I'd
probably have to to this.

This would mean, that we switch to Access 2003 runtime. Are there
any
problems together with
the runtime regarding adp/ade's?
I only heard about the missing toolbars and the missing Window to
choose Database Objects to edit them. Ah, yeah, I think I also read
about problems when trying to change Forms/Reports through Code in
DesignMode.
All of this wouldn't be a big problem as far as I can see.
Have you ever worked with Access 2003 runtime together with a
adp/ade?
If so, were there any pitfalls caused by Access 2003 runtime?
Again, thank you very much for your response!

On 8 Nov., 04:49, "Sylvain Lafontaine" <sylvain aei ca (fill the
blanks, no spam please)> wrote:

This error has been corrected in A2002 and 2003, so you must
upgrade to A2003.

For your second question, the best way is probably to check the
value on the OnBeforeUpdate event but if you want to, you could
also use the Form_Error event and check for the error 515. Of
course, this won't work with A2000, too.

http://support.microsoft.com/kb/120567/en-us

http://www.microsoft.com/technet/prodtechnol/sql/70/proddocs/diag/p
ar ...



.

Relevant Pages