> I have an A2k front end that updates itself by looking at a network
path to
> see if there are any recent updates available.
> The update file always has a name like "appupdate-yyyymmdd.mdb"
where
> yyyymmdd is the date of the update.
> The update mdb might contain new or revised forms, reports etc that
are
> imported from the existign front end so as to update itself.  Once
the
> update occurs, a field in a local table is set to the name of the
update
> field so that it won't use it to update itself again until there is
a newer
> update file available.
> In the update code, I do a DIR on the location where the updates are
placed
> to see if there are any files that match the appropriate pattern.
If DIR
> returns a zero lenght string then the update does not execute, cuz
there's
> nothting to do and teh program runs normally.  If an update file is
found,
> then the update occurs and then the program runs normally after
that.
> Here's my problem:
> All that works great.  But, for several reasons, we had to move the
> "appupdate-yyyymmdd.mdb" files to an ftp location instead of a
> \\server\updatefolder  or e:\updatefolder configuration.   I tried
doing a
> DIR function on the ftp address.  It doesn't crash, but it doesn't
find the
> file.
> the code is (where 'user' is the user and location for the ftp site
and
> password is of course the password to get in):

>     sFilePattern = "/AppUpdate*.mdb"
>     sUpdateFile = Dir(sPath & sFilePattern)
>     (then there's a bunch of code that opens up the remote mdb file
and
> imports the objects into the local mdb file)

> keep in mind that this all worked fine when it was
>     sPath = "e:\updatefolder"
>     sFilePattern = "\AppUpdate*.mdb"
>     sUpdateFile = Dir(sPath & sFilePattern)
>     (then there's a bunch of code that opens up the remote mdb file
and
> imports the objects into the local mdb file)
> or
>     sPath = "\\server\updatefolder"
>     sFilePattern = "\AppUpdate*.mdb"
>     sUpdateFile = Dir(sPath & sFilePattern)
>     (then there's a bunch of code that opens up the remote mdb file
and
> imports the objects into the local mdb file)

> but the ftp method does not work.  like i said, it doesn't crash, it
just
> doesn't seem to see the file.
> Any suggestions would be very much appreciated.

> Thanks,

> Keith