Access 2003 mde or mdb will not work with Access Runtime

[larpup]

I checked all my references prior to compiling. The mdb or mde works
perfectly with full version of A2003.

When running on a computer with RunTime i receive an error that a
reference is broken to msoutl.olb version 9.2.

Can anyone shed some light on this as I need to deploy this application
as soon as possible. Any information regarding this would be greatly
appreciated.

Regards,

Lar

[Granny Spitz via AccessMonster.com]

larpup wrote:

When running on a computer with RunTime i receive an error that a
reference is broken to msoutl.olb version 9.2.

Use late binding and make sure Outlook 2000 is installed on the computer. Be
aware that some things might not work right because of the different versions
of Office you're trying to mesh together.

--
Message posted via http://www.accessmonster.com

[larpup]

Thanks for the prompt reply.

Outlook (Office for that matter) 2000 is installed on the computer I am
installing A2003 runtime on with my mde. file. Additionaly , I noticed
that my form is producing all sorts of error messages utilizing the
runtime. (command buttons and comboboxes.) Also for a date field
receiving a $Name#.... error in a text box.

What is late binding and how can I use it? I was under the impression
that as long as you point the mde to A2003 /runtime all should be
fine..... I've used runtime A2000 with no problems. I just don't
understand. Appears all my references are correct.

Would greatly appreciate any addtional advice you have...

Lar

Granny Spitz via AccessMonster.com wrote:

larpup wrote:

When running on a computer with RunTime i receive an error that a
reference is broken to msoutl.olb version 9.2.

Use late binding and make sure Outlook 2000 is installed on the computer. Be
aware that some things might not work right because of the different versions
of Office you're trying to mesh together.

--
Message posted via http://www.accessmonster.com

[Albert D. Kallal]

The suggestion being offered is while looking at code, go tools->references.

You want to remove any stray references. Likely that mso ref you have is
also in that list...remove it.

So, remove any and all garbage references. If you have any defences to
outlook, or word, or excel, etc, you WANT TO REMOVE THEN ALSO, AND USE LATE
BINDING!

Late binding is expalined here:

http://www.granite.ab.ca/access/latebinding.htm
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com

[Granny Spitz via AccessMonster.com]

larpup wrote:

Additionaly , I noticed
that my form is producing all sorts of error messages utilizing the
runtime. (command buttons and comboboxes.) Also for a date field
receiving a $Name#.... error in a text box.

That means you have at least one missing library reference.

What is late binding and how can I use it? I was under the impression
that as long as you point the mde to A2003 /runtime all should be
fine..... I've used runtime A2000 with no problems.

Different versions of office are often located in differently named directory
paths. Libraries are hard coded in MDE files so if one of the libraries on
the Access 2003 computer used to create the MDE had the path C:\Program Files\
Microsoft Office\OFFICE11 and that same file on the Office 2000 computer used
C:\Program Files\Microsoft Office\OFFICE9, the MDE file won't find the
library file, even though it exists in a similarly named directory (OFFICE9
vs OFFICE11).

Late binding means you don't add the library to your references collection
but when you need a specific library in your code, you declare a variable as
an object type and set the variable to the appropriate library object at
runtime.

Dim olk as Object

You'll find examples of the syntax and more explanations by googling:

http://groups.google.com/groups?as_q...ugroup=*access
*

--
Message posted via http://www.accessmonster.com

[larpup]

I ensured that the path to execute the A2003 mde is correct and it does
open.... Can I use the reference "Microsoft Outlook 11 Library" on the
computer that has Office 2000, but no Access... This seems kind of
weird to me. Would I have to reference Microsoft Outlook 9 Library if
they are using Outlook 2000? and if so, will it even compile?

Lar

Granny Spitz via AccessMonster.com wrote:

larpup wrote:

Additionaly , I noticed
that my form is producing all sorts of error messages utilizing the
runtime. (command buttons and comboboxes.) Also for a date field
receiving a $Name#.... error in a text box.

That means you have at least one missing library reference.

What is late binding and how can I use it? I was under the impression
that as long as you point the mde to A2003 /runtime all should be
fine..... I've used runtime A2000 with no problems.

Different versions of office are often located in differently named directory
paths. Libraries are hard coded in MDE files so if one of the libraries on
the Access 2003 computer used to create the MDE had the path C:\Program Files\
Microsoft Office\OFFICE11 and that same file on the Office 2000 computer used
C:\Program Files\Microsoft Office\OFFICE9, the MDE file won't find the
library file, even though it exists in a similarly named directory (OFFICE9
vs OFFICE11).

Late binding means you don't add the library to your references collection
but when you need a specific library in your code, you declare a variable as
an object type and set the variable to the appropriate library object at
runtime.

Dim olk as Object

You'll find examples of the syntax and more explanations by googling:

http://groups.google.com/groups?as_q...ugroup=*access
*

--
Message posted via http://www.accessmonster.com

[Rick Brandt]

larpup wrote:

I ensured that the path to execute the A2003 mde is correct and it
does open.... Can I use the reference "Microsoft Outlook 11 Library"
on the computer that has Office 2000, but no Access... This seems
kind of weird to me. Would I have to reference Microsoft Outlook 9
Library if they are using Outlook 2000? and if so, will it even
compile?

If all computers using your app don't have the same software installed
(including the version) for the libraries you want to use code from then you
MUST use late binding so you don't have to use references. Late binding will
usually not care about the version.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

[Granny Spitz via AccessMonster.com]

larpup wrote:

Can I use the reference "Microsoft Outlook 11 Library" on the
computer that has Office 2000, but no Access... This seems kind of
weird to me. Would I have to reference Microsoft Outlook 9 Library if
they are using Outlook 2000? and if so, will it even compile?

No, don't set a reference to Outlook in the references window. In your code
use late binding by declaring a variable as an Object that at runtime will be
set to an Outlook application object like this:

Dim olk as Object
Set olk = CreateObject("Outlook.Application")
' do stuff.
Set olk = Nothing

If Outlook is installed on the computer the OS will create an instance of
Outlook, regardless of which version it is.

--
Message posted via http://www.accessmonster.com

[larpup]

Thanks for the reply... I understand.

I am using DAO.. when I load my form I get an #NAME? error on a date
field as well as others. why would that be. I am pointing the mde in
the correct direction?

Do you need exact error messages?

Lar
Granny Spitz via AccessMonster.com wrote:

larpup wrote:

Can I use the reference "Microsoft Outlook 11 Library" on the
computer that has Office 2000, but no Access... This seems kind of
weird to me. Would I have to reference Microsoft Outlook 9 Library if
they are using Outlook 2000? and if so, will it even compile?

No, don't set a reference to Outlook in the references window. In your code
use late binding by declaring a variable as an Object that at runtime will be
set to an Outlook application object like this:

Dim olk as Object
Set olk = CreateObject("Outlook.Application")
' do stuff.
Set olk = Nothing

If Outlook is installed on the computer the OS will create an instance of
Outlook, regardless of which version it is.

--
Message posted via http://www.accessmonster.com

[Granny Spitz via AccessMonster.com]

larpup wrote:

I am using DAO.. when I load my form I get an #NAME? error on a date
field as well as others. why would that be.

If an MDE works correctly on some computers but shows #NAME? on others, it
means there is VBA code or a built in function being used in the application
and at least one of the library references can't be resolved on the computers
that show #NAME?. You *must* resolve these references. The best way to do
that is to *only* use the built in references:

VBA
MS Access (version#) Object library
DAO and/or ADO

and use late binding for *all* other library objects. You have example
syntax for Outlook and if you need to use late binding for other applications
like Excel, the syntax is nearly identical:

Dim xl as Object
Set xl = CreateObject("Excel.Application")
' do stuff.
Set xl = Nothing

Do you need exact error messages?

Once you resolve the references you shouldn't have any other error messages,
but if you do please post them.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200610/1

[larpup]

Thanks for the reply..

I am using

VBA - chosen
MS Access (version#) Object library (since the program is written in 2003, library 11 is chosen, but running on a 2000 machine.
DAO and/or ADO - chosen. DAO

TO BE EXACT
VBA
Microsoft Access 11 Object Library
OLE Automation
DAO 3.6
Microsoft ActiveX data object 2.1 Library
Microsfot Outlook 11. Object Library (which I can change to late
binding.)

Any other ideas what could be wrong...

Really appreciate the advice.
Lar
Granny Spitz via AccessMonster.com wrote:

larpup wrote:

I am using DAO.. when I load my form I get an #NAME? error on a date
field as well as others. why would that be.

If an MDE works correctly on some computers but shows #NAME? on others, it
means there is VBA code or a built in function being used in the application
and at least one of the library references can't be resolved on the computers
that show #NAME?. You *must* resolve these references. The best way to do
that is to *only* use the built in references:

VBA
MS Access (version#) Object library
DAO and/or ADO

and use late binding for *all* other library objects. You have example
syntax for Outlook and if you need to use late binding for other applications
like Excel, the syntax is nearly identical:

Dim xl as Object
Set xl = CreateObject("Excel.Application")
' do stuff.
Set xl = Nothing

Do you need exact error messages?

Once you resolve the references you shouldn't have any other error messages,
but if you do please post them.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200610/1

[Rick Brandt]

larpup wrote:

Thanks for the reply..

I am using

>VBA - chosen
MS Access (version#) Object library (since the program is written in
2003, library 11 is chosen, but running on a 2000 machine. DAO
and/or ADO - chosen. DAO

TO BE EXACT
VBA
Microsoft Access 11 Object Library
OLE Automation
DAO 3.6
Microsoft ActiveX data object 2.1 Library
Microsfot Outlook 11. Object Library (which I can change to late
binding.)

Any other ideas what could be wrong...

There is no need for "other ideas". If you include a reference to Outlook
11 and that does not exist on the target PC then THAT is the problem.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

[Granny Spitz via AccessMonster.com]

larpup wrote:

OLE Automation

You can probably remove this. Are you using any of these classes or
functions in your code? If no, remove it.

Microsfot Outlook 11. Object Library (which I can change to late
binding.)

Definitely remove this.

Any other ideas what could be wrong...

Remove those references from the references collection and use late binding.
If you *still* have problems please post back.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200610/1

[larpup]

Thanks Rick,

Will work with that. Just doesn't make sense that the data wouldn't be
displayed accurated in my from. I don't see what that would have to do
with the loading the Outlook library.

Lar

Rick Brandt wrote:

larpup wrote:

Thanks for the reply..

I am using

VBA - chosen
MS Access (version#) Object library (since the program is written in
2003, library 11 is chosen, but running on a 2000 machine. DAO
and/or ADO - chosen. DAO

TO BE EXACT
VBA
Microsoft Access 11 Object Library
OLE Automation
DAO 3.6
Microsoft ActiveX data object 2.1 Library
Microsfot Outlook 11. Object Library (which I can change to late
binding.)

Any other ideas what could be wrong...

There is no need for "other ideas". If you include a reference to Outlook
11 and that does not exist on the target PC then THAT is the problem.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

[larpup]

Thanks Rick,

Will work with that. Just doesn't make sense that the data wouldn't be
displayed accurated in my from. I don't see what that would have to do
with the loading the Outlook library.

Lar

Rick Brandt wrote:

larpup wrote:

Thanks for the reply..

I am using

VBA - chosen
MS Access (version#) Object library (since the program is written in
2003, library 11 is chosen, but running on a 2000 machine. DAO
and/or ADO - chosen. DAO

TO BE EXACT
VBA
Microsoft Access 11 Object Library
OLE Automation
DAO 3.6
Microsoft ActiveX data object 2.1 Library
Microsfot Outlook 11. Object Library (which I can change to late
binding.)

Any other ideas what could be wrong...

There is no need for "other ideas". If you include a reference to Outlook
11 and that does not exist on the target PC then THAT is the problem.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

[Rick Brandt]

larpup wrote:

Thanks Rick,

Will work with that. Just doesn't make sense that the data wouldn't be
displayed accurated in my from. I don't see what that would have to do
with the loading the Outlook library.

Broken references break a LOT of stuff that has nothing to do with the
actual missing library. The built in functions messing up is what people
usually notice.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

[larpup]

Rick,
Again thanks for the help.

I am new to OOP and need a little advise (example) how to set and dim
Outlook.MailItem and Outlook.Attachement. If you could provide me with
one example of this, I'm confident I can figure the rest out.

Also, if Outlook is open I use the GetObject and if not I use the
CreateObject, yes?
Really appreciate the help.

Lar

Rick Brandt wrote:

larpup wrote:

Thanks Rick,

Will work with that. Just doesn't make sense that the data wouldn't be
displayed accurated in my from. I don't see what that would have to do
with the loading the Outlook library.

Broken references break a LOT of stuff that has nothing to do with the
actual missing library. The built in functions messing up is what people
usually notice.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

[David W. Fenton]

"larpup" <la****@gmail.comwrote in
news:11**********************@b28g2000cwb.googlegr oups.com:

Will work with that. Just doesn't make sense that the data
wouldn't be displayed accurated in my from. I don't see what that
would have to do with the loading the Outlook library.

If there's a missing reference none of the VBA code can execute.

With late binding the code can still compile.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[David W. Fenton]

"larpup" <la****@gmail.comwrote in
news:11*********************@i42g2000cwa.googlegro ups.com:

I am new to OOP

This is not really OOP.

and need a little advise (example) how to set and dim
Outlook.MailItem and Outlook.Attachement. If you could provide me
with one example of this, I'm confident I can figure the rest out.

You use generic object variables.

Also, if Outlook is open I use the GetObject and if not I use the
CreateObject, yes?

CreateObject is how you initialize the Outlook instance, assigning
it to a generic object variable.

Dim objOutlook As Object

Set objOutlook = CreateObject("Outlook.Application")

(I'm making up the name used to initialize it, since I don't know
what it really should be)

Then all properties and methods of objOutlook will be the same as
those you saw with the reference still in place.

Values assigned to variables should use the appropriate variable
type. That is, if the Outlook property returns a string or a number,
use the appropriate type. If it returns an Outlook-specific data
type, then you use either a Variant or an Object -- it depends on
the circumstances.

For instances, members of a collection would get assigned to Variant
types if you're using your variable in a For/Each loop. I'm not
exactly sure where the dividing line between Variant and Object
variables should be drawn, though. I think I know it when I see it,
but I've never done enough Outlook programming (nor recently) to
give advice on that.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[larpup]

David,

thanks for the reply. i got that far... Need to use the To,
Attachments, mailItems, etc. and am having problems using them.

I have objApp.To - does not support this method.

Can I get an example. Very new to this.

Regards,

Lar
David W. Fenton wrote:

"larpup" <la****@gmail.comwrote in
news:11*********************@i42g2000cwa.googlegro ups.com:

I am new to OOP

This is not really OOP.

and need a little advise (example) how to set and dim
Outlook.MailItem and Outlook.Attachement. If you could provide me
with one example of this, I'm confident I can figure the rest out.

You use generic object variables.

Also, if Outlook is open I use the GetObject and if not I use the
CreateObject, yes?

CreateObject is how you initialize the Outlook instance, assigning
it to a generic object variable.

Dim objOutlook As Object

Set objOutlook = CreateObject("Outlook.Application")

(I'm making up the name used to initialize it, since I don't know
what it really should be)

Then all properties and methods of objOutlook will be the same as
those you saw with the reference still in place.

Values assigned to variables should use the appropriate variable
type. That is, if the Outlook property returns a string or a number,
use the appropriate type. If it returns an Outlook-specific data
type, then you use either a Variant or an Object -- it depends on
the circumstances.

For instances, members of a collection would get assigned to Variant
types if you're using your variable in a For/Each loop. I'm not
exactly sure where the dividing line between Variant and Object
variables should be drawn, though. I think I know it when I see it,
but I've never done enough Outlook programming (nor recently) to
give advice on that.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[David W. Fenton]

"larpup" <la****@gmail.comwrote in
news:11**********************@m73g2000cwd.googlegr oups.com:

thanks for the reply. i got that far... Need to use the To,
Attachments, mailItems, etc. and am having problems using them.

I have objApp.To - does not support this method.

Can I get an example. Very new to this.

I don't program Outlook any more, so I can't help you. Perhaps
someone else can.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[larpup]

Now that I've removed the reference, I need to create an olMailItem as
well as To, Subject and Body... This is where I am having a problem.
Since the reference is not longer there, how can I define it? Any
advice on where to research or an example would be greatly appreciated.
Again, new to this so a little frustrated.

Thanks,

Lar
Granny Spitz via AccessMonster.com wrote:

larpup wrote:

OLE Automation

You can probably remove this. Are you using any of these classes or
functions in your code? If no, remove it.

Microsfot Outlook 11. Object Library (which I can change to late
binding.)

Definitely remove this.

Any other ideas what could be wrong...

Remove those references from the references collection and use late binding.
If you *still* have problems please post back.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200610/1

[Granny Spitz via AccessMonster.com]

larpup wrote:

Since the reference is not longer there, how can I define it?

You declare the variable as an object and create that object during runtime.
Example code:

http://groups.google.com/group/micro...b8cb363d145507
http://groups.google.com/group/micro...670835b2046436
http://groups.google.com/group/micro...915499056c0f0c

Again, new to this so a little frustrated.

I don't blame you. It's hard! That's why so few people know how.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200610/1

[David W. Fenton]

"larpup" <la****@gmail.comwrote in
news:11*********************@i42g2000cwa.googlegro ups.com:

Now that I've removed the reference, I need to create an
olMailItem as well as To, Subject and Body... This is where I am
having a problem. Since the reference is not longer there, how can
I define it? Any advice on where to research or an example would
be greatly appreciated. Again, new to this so a little frustrated.

Dim olMailItem As Variant

OR

Dim olMailItem As Object

I'm not sure which is more appropriate.

The point is: you need to use pure Access data types, and none of
the ones native to Outlook, since without the reference, you can't
use it.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[larpup]

Thanks,

I will do my research.. Appreciate everyones help and advice.....

Regards,

Lar
On Oct 28, 2:15 pm, "David W. Fenton" <[e-mail]>
wrote:

"larpup" <[e-mail] innews:11*********************@i42g2000cwa.googleg roups.com:

Now that I've removed the reference, I need to create an
olMailItem as well as To, Subject and Body... This is where I am
having a problem. Since the reference is not longer there, how can
I define it? Any advice on where to research or an example would
be greatly appreciated. Again, new to this so a little frustrated.Dim olMailItem As Variant

OR

Dim olMailItem As Object

I'm not sure which is more appropriate.

The point is: you need to use pure Access data types, and none of
the ones native to Outlook, since without the reference, you can't
use it.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[larpup]

Thanks for advice and really appreciate the direction.

Regards,

Lar
On Oct 28, 9:23 am, "Granny Spitz via AccessMonster.com" <u26473@uwe>
wrote:

larpup wrote:

Since the reference is not longer there, how can I define it?You declare the variable as an object and create that object during runtime.

Example code:

http://groups.google.com/group/micro...gettingstarted...

http://groups.google.com/group/micro...activexcontrol...

http://groups.google.com/group/micro...formscoding/br...

Again, new to this so a little frustrated.I don't blame you. It's hard! That's why so few people know how.

--
Message posted via AccessMonster.comhttp://www.accessmonster.com/Uwe/Forums.aspx/databases-ms-access/2006...

[Lyle Fairfield]

"larpup" <la****@gmail.comwrote in
news:11**********************@m73g2000cwd.googlegr oups.com:

I will do my research.. Appreciate everyones help and advice.....

Unless there is some reason to use Outlook research CDO too. Outlook is
just crap as an application and super-crap when automated.

--
Lyle Fairfield

from http://msdn.microsoft.com/library/de...l=/library/en-
us/dnmdac/html/data_mdacroadmap.asp

Obsolete Data Access Technologies
Obsolete technologies are technologies that have not been enhanced or
updated in several product releases and that will be excluded from future
product releases. Do not use these technologies when you write new
applications. When you modify existing applications that are written using
these technologies, consider migrating those applications to ADO.NET.
The following components are considered obsolete:
....
Data Access Objects (DAO): DAO provides access to JET (Access) databases.
This API can be used from Microsoft Visual Basic®, Microsoft Visual C++®,
and scripting languages. It was included with Microsoft Office 2000 and
Office XP. DAO 3.6 is the final version of this technology. It will not be
available on the 64-bit Windows operating system.
.....

[Granny Spitz via AccessMonster.com]

larpup wrote:

Thanks for advice and really appreciate the direction.

You're welcome, Lar. Good luck with your application.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200610/1

[Larry Linson]

"larpup" <la****@gmail.comwrote

Will work with that. Just doesn't make sense
that the data wouldn't be displayed accurated
in my from. I don't see what that would have
to do with the loading the Outlook library.

References are like apples: one bad one can spoil the whole barrel.

That means, you may see errors in some other library whose Reference is
perfectly valid, rather than the one that is Missing.

Larry Linson
Microsoft Access MVP

[Larry Linson]

"Lyle Fairfield" <ly***********@aim.comwrote

>I will do my research.. Appreciate everyones help
and advice.....

Unless there is some reason to use Outlook research
CDO too. Outlook is just crap as an application and
super-crap when automated.

And, it is a prime target for every author of e-mail or news malware because
it is on so many computers. I keep no "address book" in either Outlook or
Outlook Express because I don't want to be the cause of attacks on my
correspondents should my computer happen to be infected with some sort of
malware.

Larry

[Lyle Fairfield]

"Larry Linson" <bo*****@localhost.notwrote in
news:zce1h.6842$HY5.1209@trnddc06:

And, it is a prime target for every author of e-mail or news malware
because it is on so many computers. I keep no "address book" in
either Outlook or Outlook Express because I don't want to be the cause
of attacks on my correspondents should my computer happen to be
infected with some sort of malware.

Sounds like a good idea!

--
Lyle Fairfield

[Granny Spitz via AccessMonster.com]

Larry Linson wrote:

I keep no "address book" in either Outlook or
Outlook Express because I don't want to be the cause of attacks on my
correspondents should my computer happen to be infected with some sort of
malware.

I have no address book for the same reason on my home computers, but I have
so few people I email from home on a regular basis it's not a problem. I
think others who have a wider circle of contacts would find this *very*
inconvenient.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200610/1

[Larry Linson]

"Granny Spitz via AccessMonster.com" wrote

>I keep no "address book" in either Outlook or
Outlook Express because I don't want to be the
cause of attacks on my correspondents should
my computer happen to be infected with some
sort of malware.

I have no address book for the same reason on
my home computers, but I have so few people I
email from home on a regular basis it's not a prob-
lem. I think others who have a wider circle of
contacts would find this *very* inconvenient.

I have an address list, just not in a place where the malware would easily
be able to make use of it.

Larry

[Granny Spitz via AccessMonster.com]

Larry Linson wrote:

I have an address list, just not in a place where the malware would easily
be able to make use of it.

That's a good way to outsmart them! Thanks for the tip.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200610/1