Hello,
I'm working on a smal DB which will act as a kind of an updater against
another db installed on users pc's.
This updaters will make changes/corrections to their data.
I would like to have this small db to write the actions taken on data on a
.txt file in order to let know the user what was going wrong with his data.
I wrote this code:

Option Compare Database
Private F As Object
Private wrkSec As Workspace
Private DBEng As Object
Private DBdaAgg As Database
Private centro As String
______________________________

Private Sub Command0_Click()
On Error GoTo HANDLER

Set fs = CreateObject("SCRIPTING.FILESYSTEMOBJECT")
Dim FirstAction As String
Dim STATUS As Boolean
Dim wrkSec As Workspace
Dim QualePath As String
Dim TBLdaAgg As DAO.Recordset
Dim TBLmaster As DAO.Recordset
Dim logStringa As String
Dim ErrorLine As Byte
Set DBEng = CreateObject("DAO.DBEngine.36")
Set F = fs.CREATETEXTFILE("C:\FARUS\LOG_20MAY2007.TXT", True)
F.writeline ("*********************************************")
F.writeline ("**           UPDATER DEL 20 MAGGIO 2007 (R)                **")
F.writeline ("*********************************************")
(other code follows)

but after many googling it comes out that it the SCRIPTING.FILESYSTEMOBJECT
is mostly used with ASP.
WHat has driven me crazy is that it worked fine on my pc and on other pcs
without the need to referencing any new .dll. But it doesn't run on user
machine: they all got error messages.
I cannot use WORD trough automation since most of the user have Access
runtime (I have deployes the db using the package wizard) and they don't have
Office installed.
I would simply use NotePad to create a .txt file to show what changes has
been done to data and to give hints to the users.

Is there any way to achieve this?

Thanks,
Rocco