By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,863 Members | 879 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,863 IT Pros & Developers. It's quick & easy.

Upload of database to ftp-server

P: n/a
Hi

I am building a simple database system in MS Access 2002 and would
like to create a command button that upon clicking transfers the
current mdb-file to an ftp-server. Is there a solution for this in MS
Access 2002 or do you have any other suggestions to solve this issue?

// Mattias
Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a

Mattias,

On 30 Sep 2003 10:33:40 -0700, mn**@hotmail.com (Mattias) wrote in
comp.databases.ms-access:
I am building a simple database system in MS Access 2002 and would
like to create a command button that upon clicking transfers the
current mdb-file to an ftp-server. Is there a solution for this in MS
Access 2002 or do you have any other suggestions to solve this issue?


You're going to have a problem sending the file that is currently
executing code, no? You *could* do this but it would be very unwise.
It's never smart to make a copy of an in-use Access database, whether
the destination is on the local pc or a remote ftp server.

You really need that button to close the current file and then trigger
a transfer from a separate executable. Of course, it's hard to
understand why you would need to send the front-end to an ftp server
anyway. It's the back-end you'd typically want to send, and that's a
whole lot easier because you don't need to close the current
code-executing mdb to send the second file.

If you have the code and data in the same mdb, then setting up the ftp
transfer is the least of your problems. A more pressing one is to
establish a proper configuration for the application in the first
place.

Peter Miller
__________________________________________________ __________
PK Solutions -- Data Recovery for Microsoft Access/Jet/SQL
Free quotes, Guaranteed lowest prices and best results
www.pksolutions.com 1.800.987.7716 1.619.839.3900
Nov 12 '05 #2

P: n/a
Thanks for the answer! You're right about that it isn't so smart to
upload an in-use mdb-file. :) I never thought about that Access have
to be closed and the file have to be saved properly before uploading
it.

The reason for uploading the mdb-file is that the information in the
database is shown at a webpage. My thought is that the user input
information about for example rooms and reservations via a form in a
local Access mdb-file and then click on a button which upload the file
to an FTP-folder so the updated reservations are shown on the webpage.
I.E, I don't want the user to open an FTP-program every time he has
input new reservations. There must be an easier way for a user to
upload a specific file to an FTP-server? Do you have any suggestions
on how to do this as easy as possible for the user?

Btw, I don't really understand what you meant by front-end and
back-end in this case.

/Mattias, Sweden
Peter Miller <pm*****@pksolutions.com> wrote in message news:<dj********************************@4ax.com>. ..
Mattias,

On 30 Sep 2003 10:33:40 -0700, mn**@hotmail.com (Mattias) wrote in
comp.databases.ms-access:
I am building a simple database system in MS Access 2002 and would
like to create a command button that upon clicking transfers the
current mdb-file to an ftp-server. Is there a solution for this in MS
Access 2002 or do you have any other suggestions to solve this issue?


You're going to have a problem sending the file that is currently
executing code, no? You *could* do this but it would be very unwise.
It's never smart to make a copy of an in-use Access database, whether
the destination is on the local pc or a remote ftp server.

You really need that button to close the current file and then trigger
a transfer from a separate executable. Of course, it's hard to
understand why you would need to send the front-end to an ftp server
anyway. It's the back-end you'd typically want to send, and that's a
whole lot easier because you don't need to close the current
code-executing mdb to send the second file.

If you have the code and data in the same mdb, then setting up the ftp
transfer is the least of your problems. A more pressing one is to
establish a proper configuration for the application in the first
place.

Peter Miller
__________________________________________________ __________
PK Solutions -- Data Recovery for Microsoft Access/Jet/SQL
Free quotes, Guaranteed lowest prices and best results
www.pksolutions.com 1.800.987.7716 1.619.839.3900

Nov 12 '05 #3

P: n/a

<Snip>

Btw, I don't really understand what you meant by front-end and
back-end in this case.

A database should be split into 2 parts; the user interface (front-end) and
the data (back-end). The back-end only has tables where all the data is
stored. The front-end holds all the queries, forms, reports etc. and has
linked tables to the back-end. In Access there is a wizard that will split
the database for you, in A2000 it's under Tools>Database Utilities>Database
Splitter.

One of the advantages of splitting the database is so that the data can be
stored in one location i.e. on a server or dedicated desktop, and all the
users have their own copies of the front-end on their PCs all linked to the
back-end. This way you can make changes to the forms etc and place this new
copy of the front-end on everybody's PCs without being too concerned about
destroying any data.

I'm not too familiar with web DBs but wouldn't you just upload the data file
(back-end) because the web page has been designed around that table
structure.

Stewart
Nov 12 '05 #4

P: n/a
Thanks for the explanation of front- and back-end and how to split the
Access database file, Stewart. But the main question remains, I.E how
to be able to upload/transfer the mdb-file to the FTP-folder
(preferably from the Access form) without opening an FTP-program. It
would be great if it's possible.

/Mattias

"Stewart Allen" <sa****@REMOVETHISwave.co.nz> wrote in message news:<bl**********@news.wave.co.nz>...
<Snip>

Btw, I don't really understand what you meant by front-end and
back-end in this case.

A database should be split into 2 parts; the user interface (front-end) and
the data (back-end). The back-end only has tables where all the data is
stored. The front-end holds all the queries, forms, reports etc. and has
linked tables to the back-end. In Access there is a wizard that will split
the database for you, in A2000 it's under Tools>Database Utilities>Database
Splitter.

One of the advantages of splitting the database is so that the data can be
stored in one location i.e. on a server or dedicated desktop, and all the
users have their own copies of the front-end on their PCs all linked to the
back-end. This way you can make changes to the forms etc and place this new
copy of the front-end on everybody's PCs without being too concerned about
destroying any data.

I'm not too familiar with web DBs but wouldn't you just upload the data file
(back-end) because the web page has been designed around that table
structure.

Stewart

Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.