FindWIndow and trademark symbol

[lauren quantrell]

I have an Access application with the name: MyAppName®
It has the "®" symbol (ChrW$(&H00AE)) at the end of it.
If I remane the application without the "®" symbol, I can use
FindWindow to close the application, but with the "®" symbol it
doesn't. Unfortunaetley this app is already distributed as MyAppName®
and I cannot change it.
I have tried:
hwnd = FindWindow(vbNu llString, "myAppName" & ChrW$(&H00AE))
But it won't work.
Yikes.
This has become an emergency.
Can anyone help?
lq

[Trevor Best]

lauren quantrell wrote:

I have an Access application with the name: MyAppName®
It has the "®" symbol (ChrW$(&H00AE)) at the end of it.
If I remane the application without the "®" symbol, I can use
FindWindow to close the application, but with the "®" symbol it
doesn't. Unfortunaetley this app is already distributed as MyAppName®
and I cannot change it.
I have tried:
hwnd = FindWindow(vbNu llString, "myAppName" & ChrW$(&H00AE))
But it won't work.
Yikes.
This has become an emergency.
Can anyone help?
lq

Can you not use the classname of the window? i.e. the first parameter,
this is after all unique.

--
This sig left intentionally blank

[lauren quantrell]

Trevor,
The application I want to close in an Access application and the user
may have many different Access applications open. As I understand it,
that precludes the use of the classname of the window...
lq

Trevor Best wrote:

lauren quantrell wrote:

I have an Access application with the name: MyAppName®
It has the "®" symbol (ChrW$(&H00AE)) at the end of it.
If I remane the application without the "®" symbol, I can use
FindWindow to close the application, but with the "®" symbol it
doesn't. Unfortunaetley this app is already distributed as MyAppName® and I cannot change it.
I have tried:
hwnd = FindWindow(vbNu llString, "myAppName" & ChrW$(&H00AE))
But it won't work.
Yikes.
This has become an emergency.
Can anyone help?
lq

Can you not use the classname of the window? i.e. the first

parameter, this is after all unique.

--
This sig left intentionally blank

[Lyle Fairfield]

lauren quantrell wrote:

I have an Access application with the name: MyAppName®
It has the "®" symbol (ChrW$(&H00AE)) at the end of it.
If I remane the application without the "®" symbol, I can use
FindWindow to close the application, but with the "®" symbol it
doesn't. Unfortunaetley this app is already distributed as MyAppName®
and I cannot change it.
I have tried:
hwnd = FindWindow(vbNu llString, "myAppName" & ChrW$(&H00AE))
But it won't work.
Yikes.
This has become an emergency.
Can anyone help?
lq

I think "®" is ChrW$(&HAE)).

in any case

"myAppName" & ChrW$(&HAE)) finds a window for me.
(haven't tried to close it).

so does

"myAppName® "
--
--
Lyle
--
From ADO28.chm

Deprecated Components
Each of the following components is considered obsolete. While these
components are still supported in this release of the Microsoft® Data
Access Components (MDAC), they may be removed in the future. When
writing new applications, you should avoid using these deprecated
components. When modifying existing applications, you are strongly
encouraged to remove any dependency on these components.

ODBC Provider (MSDASQL)
You are strongly encouraged to use one of the native OLE DB Providers
instead of the Microsoft Open Database Connectivity (ODBC) Provider.
Native OLE DB Providers provide better application stability and
performance. Furthermore, native OLE DB Providers will be supported in
the future, whereas MSDASQL will not have any new features added to it,
will not be available on 64-bit, and will not be accessible from the OLE
DB NET Data Provider.

Remote Data Services (RDS)
Remote Data Services (RDS) is a proprietary Microsoft mechanism for
accessing remote data across the Internet or intranet. Microsoft is now
shipping the Microsoft Simple Object Access Protocol (SOAP) Toolkit 2.0
that enables you to access remote data using an open, XML-based
standard. Given the availability of the SOAP Toolkit 2.0, you should
migrate from RDS to SOAP. The SOAP 2.0 Toolkit 2.0 also includes sample
code for remotely accessing Microsoft ActiveX® Data Objects (ADO)
Recordsets.

Jet and Replication Objects (JRO)
The Microsoft Jet OLE DB Provider and other related components were
removed from MDAC 2.6. Microsoft has deprecated the Microsoft Jet
Engine, and plans no new releases or service packs for this component.
As a result, the Jet and Replication Objects (JRO) is being deprecated
in this release and will not be available in any future MDAC releases.

.....

[Trevor Best]

lauren quantrell wrote:

Trevor,
The application I want to close in an Access application and the user
may have many different Access applications open. As I understand it,
that precludes the use of the classname of the window...
lq

When you say

Unfortunaetley this app is already distributed as

MyAppName®

and I cannot change it.

Do you mean the whole app or just the caption?

--
This sig left intentionally blank

[lauren quantrell]

Lyle,
(&H00AE) converts to (&HAE) when compiled.
I can find the window, and it gives me a hwnd number, but for some
reason it doesn't close it, but it will only close it if the
application has no "®". Very puzzling.
lq

Lyle Fairfield wrote:

lauren quantrell wrote:

I have an Access application with the name: MyAppName®
It has the "®" symbol (ChrW$(&H00AE)) at the end of it.
If I remane the application without the "®" symbol, I can use
FindWindow to close the application, but with the "®" symbol it
doesn't. Unfortunaetley this app is already distributed as MyAppName® and I cannot change it.
I have tried:
hwnd = FindWindow(vbNu llString, "myAppName" & ChrW$(&H00AE))
But it won't work.
Yikes.
This has become an emergency.
Can anyone help?
lq
I think "®" is ChrW$(&HAE)).

in any case

"myAppName" & ChrW$(&HAE)) finds a window for me.
(haven't tried to close it).

so does

"myAppName® "
--
--
Lyle
--
From ADO28.chm

Deprecated Components
Each of the following components is considered obsolete. While these
components are still supported in this release of the Microsoft®

Data Access Components (MDAC), they may be removed in the future. When
writing new applications, you should avoid using these deprecated
components. When modifying existing applications, you are strongly
encouraged to remove any dependency on these components.

ODBC Provider (MSDASQL)
You are strongly encouraged to use one of the native OLE DB Providers instead of the Microsoft Open Database Connectivity (ODBC) Provider.
Native OLE DB Providers provide better application stability and
performance. Furthermore, native OLE DB Providers will be supported in the future, whereas MSDASQL will not have any new features added to it, will not be available on 64-bit, and will not be accessible from the OLE DB NET Data Provider.

Remote Data Services (RDS)
Remote Data Services (RDS) is a proprietary Microsoft mechanism for
accessing remote data across the Internet or intranet. Microsoft is now shipping the Microsoft Simple Object Access Protocol (SOAP) Toolkit 2.0 that enables you to access remote data using an open, XML-based
standard. Given the availability of the SOAP Toolkit 2.0, you should
migrate from RDS to SOAP. The SOAP 2.0 Toolkit 2.0 also includes sample code for remotely accessing Microsoft ActiveX® Data Objects (ADO)
Recordsets.

Jet and Replication Objects (JRO)
The Microsoft Jet OLE DB Provider and other related components were
removed from MDAC 2.6. Microsoft has deprecated the Microsoft Jet
Engine, and plans no new releases or service packs for this component. As a result, the Jet and Replication Objects (JRO) is being deprecated in this release and will not be available in any future MDAC releases.
....

[lauren quantrell]

Trevor,
The application is in the hands of a few hundred users globally and I
already have the caption with the "®" symbol.
lq

[Trevor Best]

lauren quantrell wrote:

Trevor,
The application is in the hands of a few hundred users globally and I
already have the caption with the "®" symbol.

I was going to suggest some sort of workaround where you could open the
other Access mdb, pop in a value to a table that a timer event in the
other app would react to. If you can't change that app at all then
that's not an option :-(

--
This sig left intentionally blank

[Lyle Fairfield]

"lauren quantrell" <la************ *@hotmail.com> wrote in
news:11******** **************@ z14g2000cwz.goo glegroups.com:

Lyle,
(&H00AE) converts to (&HAE) when compiled.
I can find the window, and it gives me a hwnd number, but for some
reason it doesn't close it, but it will only close it if the
application has no "®". Very puzzling.
lq

How do you try to close it?

I use:

Dim h As Long
h = FindWindow(vbNu llString, "MyApplicationT itle" & ChrW$(&HAE))
PostMessage h, WM_CLOSE, 0, 0

with the requisite API declarations. Of course, one can use the IsWindow
and WaitForSingleOb ject functions to be sure or branch somewhere else if
unsuccessful.

--
Lyle
--

[lauren quantrell]

Lyle,
I use:
Dim hwnd as long
hwnd = FindWindow(vbnu llstring,"AppNa me" & ChrW$(&HAE))
SetForegroundWi ndow hwnd
PostMessage hwnd, WM_CLOSE, 0&, 0&

lq

Lyle Fairfield wrote:

"lauren quantrell" <la************ *@hotmail.com> wrote in
news:11******** **************@ z14g2000cwz.goo glegroups.com:

Lyle,
(&H00AE) converts to (&HAE) when compiled.
I can find the window, and it gives me a hwnd number, but for some
reason it doesn't close it, but it will only close it if the
application has no "®". Very puzzling.
lq
How do you try to close it?

I use:

Dim h As Long
h = FindWindow(vbNu llString, "MyApplicationT itle" & ChrW$(&HAE))
PostMessage h, WM_CLOSE, 0, 0

with the requisite API declarations. Of course, one can use the

IsWindow and WaitForSingleOb ject functions to be sure or branch somewhere else if unsuccessful.

--
Lyle
--