VO28 _DLL ACCESS error

Fred Killet

unread,

Oct 15, 2012, 7:05:09 AM10/15/12

to

Hello,

I use some ACCESS and ASSIGN statements in an interface for my Graphics4VO
DLL like this:

_DLL ACCESS Background CLASS
gFormPushButton:graphlib.gFormPushButton:Background:ACCESS

This works fine in VO27. But in VO28 an error message comes up when I start
the executable which is using the DLL:

"The procedure entrence point 'gFormPushButton:Background:ACCESS' could not
found in the DLL 'graphlib.DLL'".

Is that an bug in VO28? Is there a workaround? Thank you for your help.
--

Kind regards
Fred
killet...@killetsoft.de

Malcolm G

unread,

Oct 15, 2012, 8:07:38 AM10/15/12

to

On 15/10/2012 12:05, Fred Killet wrote:
> Hello,
>
> I use some ACCESS and ASSIGN statements in an interface for my Graphics4VO
> DLL like this:
>
> _DLL ACCESS Background CLASS
> gFormPushButton:graphlib.gFormPushButton:Background:ACCESS

> This works fine in VO27. But in VO28 an error message comes up when I start
> the executable which is using the DLL:

I take it this is a manually written _DLL line?
Are you sure the case of that line is the same in Vo27 and VO28?
Are you sure the case of line it refers to is the same in Vo27 and VO28?
Have you used a tool like depends to check?

Fred Killet

unread,

Oct 15, 2012, 8:32:33 AM10/15/12

to

Hi Malcolm,

> I take it this is a manually written _DLL line?

No, it is generated by VO2.8 SP4 and then copied to my own DLL-interface.

> Are you sure the case of that line is the same in Vo27 and VO28?

Yes, it is realy the same.

> Are you sure the case of line it refers to is the same in Vo27 and VO28?

Yes, the lines are identical.

> Have you used a tool like depends to check?

no I have no such tool.

Here is the source of ACESS Background which is identical in VO27 and VO28:

ACCESS Background CLASS gFormPushButton
// Überschreibt die Access-Methode der Klasse control{}
RETURN SELF:_oBackBrush

Here is the DLL interface to that ACCESS:

_DLL ACCESS Background CLASS
gFormPushButton:graphlib.gFormPushButton:Background:ACCESS

I have the source lines copied and pasted from the original source because I
wanted to avoid typing errors.
--

Regards,
Fred Killet
killet...@killetsoft.de

Malcolm G

unread,

Oct 15, 2012, 8:51:08 AM10/15/12

to

On 15/10/2012 13:32, Fred Killet wrote:

>> Have you used a tool like depends to check?
> no I have no such tool.

I have to suggest you get it then:
http://www.dependencywalker.com/
as it will let you see what the DLL exports.

one other thing I have tried in the past with various versions of VO
is to touch the problem entity and recompile in case it forgot to export it.

Fred Killet

unread,

Oct 15, 2012, 10:02:38 AM10/15/12

to

Hi Malcolm,

> one other thing I have tried in the past with various versions of VO
> is to touch the problem entity and recompile in case it forgot to export
> it.

I have checked this. The bug is still present.

Now I installed Dependency Walker. Viewing the GRAPHLIB.DLL for VO28 I found
the following entrence:
107 (0x006B) 106 (0x006A) gFormPushButton:Background:Access 0x000BAE4C

"ACCESS" is here written as "Access". Is that ok?

Fred

Gerhard Bunzel

unread,

Oct 15, 2012, 10:30:27 AM10/15/12

to

Fred,

in VO28 it is not allowed, that ACCESS/ASSIGN methods have the same name as
PROTECTED or HIDDEN variables.

Maybe this is the problem.

HTH

Gerhard

"Fred Killet" <killet...@killetsoft.de> schrieb im Newsbeitrag
news:507bede8$0$6627$9b4e...@newsspool2.arcor-online.net...

Malcolm G

unread,

Oct 15, 2012, 10:32:57 AM10/15/12

to

That is the problem. I am less sure what the fix is given what you have
said.

Fred Killet

unread,

Oct 15, 2012, 12:13:23 PM10/15/12

to

The source code editor always redesigns the word "Access" to uppercase
letters "ACCESS". No change to test ist.

Fred

Fred Killet

unread,

Oct 15, 2012, 12:16:05 PM10/15/12

to

> in VO28 it is not allowed, that ACCESS/ASSIGN methods have the same name
> as PROTECTED or HIDDEN variables.

All my ACCESS and ASSIGN in my VO28 code, independent of the naming, have
the same problem.

Fred

--

Fred Killet
killet...@killetsoft.de
"Gerhard Bunzel" <g.bu...@domonet.de> schrieb im Newsbeitrag
news:k5h6lb$qrb$1...@news.m-online.net...

Fred Killet

unread,

Oct 15, 2012, 12:31:03 PM10/15/12

to

I tried it! When disabeling Tool / Options / Editor / Intellisense /
Keyword Case to "None", the word "Access" is not be redisigned to uppercase
letters. When trying to run my application using the DLL interface no error
comes up anymore.

So we found a real bug in VO28: In _DLL statements the keywords ACCESS and
ASSIGN may not be case dependent!

Thanks for your help.

Fred Killet

unread,

Oct 15, 2012, 12:50:41 PM10/15/12

to

The next problem: Ones changed Tools / Options / Editor / Intellisense /
Keyword Case to "None" it is not possible to change it back to "Upper case"
or to "Lower case". Any ideas?

Fred

--

Fred Killet
killet...@killetsoft.de

"Fred Killet" <killet...@killetsoft.de> schrieb im Newsbeitrag
news:507bede8$0$6627$9b4e...@newsspool2.arcor-online.net...

Fred Killet

unread,

Oct 15, 2012, 12:59:03 PM10/15/12

to

Sorry! I forgot to enable Tools / Options / Editor / Intellisense / Case
Synchronization to "Yes". The behavior is correct.

Fred

Dirk (Belgium)

unread,

Oct 16, 2012, 4:12:28 AM10/16/12

to

Hello Fred,

This behavior is not only in VO2.8; but it is in all VO-version.

Let me explain: You have generated the code automaticly, and then you
have copy/paste this code. During the paste operation, uppercasing is
done (which is the problem).

Disabling the words ACCESS and ASSIGN to automaticly uppercasing is not
a good idea.

Maybe disabling the :ACCESS and :ASSIGN is a better idea.

Dirk (Belgium)

=======================

Fred Killet

unread,

Oct 18, 2012, 1:24:22 AM10/18/12

to

Hi Dirk,

how to do the disabling of the strings ":ACCESS" and ":ASSIGN" ?.

Fred

--

Fred Killet
killet...@killetsoft.de

"Dirk (Belgium)" <dirk.dot....@pbprojects.dot.be> schrieb im
Newsbeitrag news:k5j4tc$gjv$1...@dont-email.me...