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

[Stefan]

Property or method not found

Hi everybody!

We're planning to start a new Project using Access 2000 adp. In the
Prototype we detected a problem.

Situation:
Subform (continuous form) based on a single table. The Subform is
linked to the main form through a control.

Whenever trying to insert an invalid record in the subform (eg. one
that violates the primary key constraint, or tries to insert a null
value into a column that can't be null) we get a strange error:
"There was a problem accessing a property or method of the OLE
object[...]" (Error Code: 2757)

Im aware of the microsoft Knowledge Base Article (Q301693):
http://support.microsoft.com/?scid=kb;en-us;301693&x=17&y=21

But unfortunately this does only work, when the Subform is opened alone
(outside main form).


Has anybody a solution to this Problem? If we can't solve this Problem,
this would likely disqualify using Access 2000 ADP ....

 

[Stefan]

I would also be glad to read how other persons came around that OLE
Error.

Is there only the solution of checking the values in VB before Update?

Every feedback is highly appreciated!

 

[Sylvain Lafontaine]

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/part3/75528c13.mspx?mfr=true

 

[Stefan]

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!

 

[Sylvain Lafontaine]

Sorry but I don't use the runtime, so I cannot tell you more about this. I
always suggest to my clients to buy a full copy of Access instead of using
the runtime (even if I have it) because you never know when they may need it
in a hurry because of some error, to make a quick correction or for
something funny like adding a christmas tree to a report.

However, I would be surprised if you find yourself having some problem with
the runtime that's not there with the full copy of Access (exceprt of course
for the missing toolbar and database window). Finally, don't forget that
Access 2007 is around the corner.

 

[Stefan]

Hi Sylvain,

Thanks for your answers!

I think the users can live with the limited functionality...

kind Regards,

Stefan

 

[bas]

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

 

[Stefan]

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]

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

 

[Stefan]

Hi bas,

thank you!

I'm sure, this was not my last post in this newsgroup

regards,

Stefan