DHTML EDIT ActiveX Control

Normalt skal man bruge shift+Enter for at lave linjeskift i kontroller i Access.
Du kan aendre key behaviour paa Enter "globalt" under Tools, der ligger en tab-side for keyboard under options. Men denne aendirng vil koere igenenm for alle databaser paa din pc

-> Overchord. Du skriver "Normalt skal man bruge shift+Enter for at lave linjeskift i kontroller i Access"
Det passer da ikke. Hvis du for text boxen angiver "Enter Key Behavior" til "New Line in Field" så får du et linieskift, altså en ny linie. Denne option er bare ikke tilgængelig i DHTML Editor Controlleren.

At ændre "Enter Key Behavior" under option for databasen virker ikke i DHTML Edit Controllen!

Jeg kan ihvertfald ikke få det til at virke på min maskine.
Har du selv prøvet din løsning af eller var det et forslag jeg kunne prøve af?

/Jesper

Nope det var abre et foreslag...

Er der virkelig ikke nogle der har arbejdet med DHTML Edit Control i Access og haft ligende problem og som har en løsning ??

Kom nu! Der må være nogle små eksperter i VBA programmering, der kan finde en løsning!!

/Jesper

I have NEVER had the need for using the DHTML Edit Control so I wouldnt know where to start. I would be very surprised if many others use it either!

Det har du nok ret i.

Jeg lader spørgsmålet stå åbnet et par dage endnu. Det kan jo være en VBA freak får mod på at finde en løsning på problemstillingen  :-)

/Jesper

Jesper, I have actually had a look at the problem and it looks to me as though it is the control which has the problem! The control should take ALL key events so that focus doesnt go to the next control, but I cant see any paramaters to alter this.

Terry, If I use the control in a VB 6 project, the problem is not there. Here the control works perfect. When you hit the return key, you will get a new line.

If you want to play a little with it, I can send you the DHTMLEdit SDK. There is also included some samples for VB and Internet Explorer.

/Jesper

Jesper I would prefer not to, thanks though!
Controls designed for VB are not always compatible with Access even though they are accessible in the Toolbox, I think this is the case here!

Yes - It can be! Anyway thanks for your help!

No problem Jesper, if I had more time I would look more closely at this but I  dont :o(

Lukker spørgsmål, da ingen foreslag er kommet