CreateObject("Scripting.FileSystemObject") error

Hi,

I have meet a problem for CreateObject("Scripting.FileSystemObject").

I uses this code to get the information of the harddisk

I have 10 user using the same code. All where working fine excpet for 1. When
i was using it prompt this error:
"License information for this component not found. You do not have an
appropriate license to use this functionality in the design environment"

Is there a way to solve or a better method to solve this problem

Urgently needed. Please help. Thanks

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/databases-ms-ac cess/200711/1

Re: CreateObject("Scripting.FileSystemObject") error

What information are you trying to get at?

There are API calls and functions built into Access that can do almost
everything that you can get via the FileSystem object.



On Tue, 27 Nov 2007 01:28:00 GMT, "Benjamins via AccessMonster.com"
wrote:

>Hi,
>
>I have meet a problem for CreateObject("Scripting.FileSystemObject").
>
>I uses this code to get the information of the harddisk
>
>I have 10 user using the same code. All where working fine excpet for 1. When
>i was using it prompt this error:
>"License information for this component not found. You do not have an
>appropriate license to use this functionality in the design environment"
>
>Is there a way to solve or a better method to solve this problem
>
>Urgently needed. Please help. Thanks

Please Post Any Replies To This Message Back To the Newsgroup.
There are "Lurkers" around who can benefit by our exchange!

Re: CreateObject("Scripting.FileSystemObject") error

Chuck Grimsby wrote in
news:u1cpk3d4tloif71inb0u8soptajvnci6ns@4ax.com:

> What information are you trying to get at?
>
> There are API calls and functions built into Access that can do
> almost everything that you can get via the FileSystem object.

It's quite useful for checking if network shares are available.
There's no accurate way to do that with the built-in Access commands
(other than attempting to write to it, which requires cleanup).

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

Re: CreateObject("Scripting.FileSystemObject") error

On 28 Nov 2007 00:52:07 GMT, "David W. Fenton"
wrote:

>Chuck Grimsby wrote in
>news:u1cpk3d4tloif71inb0u8soptajvnci6ns@4ax.com:
>
>> What information are you trying to get at?
>>
>> There are API calls and functions built into Access that can do
>> almost everything that you can get via the FileSystem object.
>
>It's quite useful for checking if network shares are available.
>There's no accurate way to do that with the built-in Access commands
>(other than attempting to write to it, which requires cleanup).

You can use API calls for that, David. No problem. NetShareEnum, for
example, shows what shares are available.

Please Post Any Replies To This Message Back To the Newsgroup.
There are "Lurkers" around who can benefit by our exchange!

Re: CreateObject("Scripting.FileSystemObject") error

Chuck Grimsby wrote in
news:db2sk3pdi8ppoged7bb78s28jsd5uo7501@4ax.com:

> On 28 Nov 2007 00:52:07 GMT, "David W. Fenton"
> wrote:
>
>>Chuck Grimsby wrote in
>>news:u1cpk3d4tloif71inb0u8soptajvnci6ns@4ax.com:
>>
>>> What information are you trying to get at?
>>>
>>> There are API calls and functions built into Access that can do
>>> almost everything that you can get via the FileSystem object.
>>
>>It's quite useful for checking if network shares are available.
>>There's no accurate way to do that with the built-in Access
>>commands (other than attempting to write to it, which requires
>>cleanup).
>
> You can use API calls for that, David. No problem. NetShareEnum,
> for example, shows what shares are available.

With late binding of the FSO, what's the downside? It's easy and
fast without needing to have the API code loaded. What am I missing?

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

Re: CreateObject("Scripting.FileSystemObject") error

On 30 Nov 2007 00:29:46 GMT, "David W. Fenton"
wrote:

>Chuck Grimsby wrote in
>news:db2sk3pdi8ppoged7bb78s28jsd5uo7501@4ax.com:
>
>> On 28 Nov 2007 00:52:07 GMT, "David W. Fenton"
>> wrote:
>>
>>>Chuck Grimsby wrote in
>>>news:u1cpk3d4tloif71inb0u8soptajvnci6ns@4ax.com:
>>>
>>>> What information are you trying to get at?
>>>>
>>>> There are API calls and functions built into Access that can do
>>>> almost everything that you can get via the FileSystem object.
>>>
>>>It's quite useful for checking if network shares are available.
>>>There's no accurate way to do that with the built-in Access
>>>commands (other than attempting to write to it, which requires
>>>cleanup).
>>
>> You can use API calls for that, David. No problem. NetShareEnum,
>> for example, shows what shares are available.
>
>With late binding of the FSO, what's the downside? It's easy and
>fast without needing to have the API code loaded. What am I missing?

Using the FSO loads a bunch of stuff that isn't needed.
The FSO calls those APIs anyways, so there's a layer that's skipped as
well. Granted, that's not all that important anymore in these days of
cheap memory, but I'm "old school" about that.

I also remember the days when scripting was routinely blocked by
Network Admins on most computers. That's not so true these days, NAs
and IT Departments have come to trust (and rely on!) scripts to do the
simplest of things, but old habits die hard. And I do still
occasionally run into conditions where scripts aren't allowed. No one
blocks API calls, so....

What's the upside of using the FSO?

Please Post Any Replies To This Message Back To the Newsgroup.
There are "Lurkers" around who can benefit by our exchange!

Re: CreateObject("Scripting.FileSystemObject") error

Chuck Grimsby wrote in
news:1u31l3th958mh45aboub60uh5285ahdb97@4ax.com:

> What's the upside of using the FSO?

Fewer lines of code.

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

Re: CreateObject("Scripting.FileSystemObject") error

"David W. Fenton" schreef in bericht =
news:Xns99FC9E49B86C1f99a49ed1d0c49c5bbb2@66.250.146.128...
> Chuck Grimsby wrote in
> news:1u31l3th958mh45aboub60uh5285ahdb97@4ax.com:=20
>=20
>> What's the upside of using the FSO?
>=20
> Fewer lines of code.
>=20
> --=20

David, did you change your mind on the WSH - issue ??
I remember you telling here to disable the WSH scripting host...

Or am I missing something here ?? FSO means WSH right ??

Arno R