Updating the back-end for client

[DavidG]

I have an application where I did the typical front-end/back-end split.
I've come into an issue where I need to update (in my case append only)
data to the back-end file. The task doesn't seem to warrant creating
code suitatable for a novice user, but emailing the back-end file back
and forth is not a desireable alternative either.

I wanted to see if others have come across this same situation and how
they handled it.

Thanks in advance

 

[Albert D. Kallal]

Is this a data only update?

I would simply either :

a) if competent users, simply given them instructions on how to open
the back end, and go file->get external data, and import.


b) simply send them a mdb file with a linked table to the back end,
and they press a update button. If the back location is not known, then you
can use your same re-link code (that you NO DOUBT implemented years ago to
deal with the new FE that you send to the clients. So, you likely had to
deal with fix, and write a re-link table routine that you use for all of
your applications. So, just include that re-link code, and a linked table +
the data in a mdb file. You send it to tem. They run it..it links to the
back end table, and has a start-up form with button to "merge data" to the
table....

 

[Guest]

David,

See my BE Update Utility.mdb at -

http://www.rogersaccesslibrary.com/OtherLibraries.asp#Hibbs,Peter S

which, I believe, does just what you want.

 

[dbahooker]

if you had a real database-- like SQL Server then you could use ALTER
SCRIPTS in order to do anything that you wanted

MDB isn't adequate for real world use ANYWHERE

Spit on anyone that uses it.

Access Data Projects made MDB obsolete 10 years ago..
and MDB isnt included in the next version of Office.. do you really
want to rewrite your apps AGAIN?

Use Access Data Projects

-Aaron

 

[DavidG]

Thanks for your comments. You are correct, there is code in my front
end to seek out the back end file or request the user navigate to the
correct sub-directory, then establish the table links.

I can use the same code from a temporary front end .mdb file (which
has the data to be appended in it) and add code to append the data from
the temporary file to the back end without concern for the competence
of the user.

Thanks again.

 

[DavidG]

Thanks for your comments and link. In my case I am only appending data
and not modifying the back end table structures or relationships. I
believe your utility handles structural changes only.

 

[DavidG]

You may be right, but sometimes you have to work with the tools a
particular client has access to. Especially when the client is only a
small department in a large corporation.

 

[John Vinson]

I have an application where I did the typical front-end/back-end split.
I've come into an issue where I need to update (in my case append only)
data to the back-end file.

I'm confused. You have all the tables in the backend linked, no?
Surely you can run an Append query appending to the linked table -
which is the backend table, viewed through the link?

I don't see why there's any need to open the backend at all, if it's
just appending data into an existing table!

John W. Vinson[MVP]

 

[DavidG]

Surely you can run an Append query appending to the linked table -
which is the backend table, viewed through the link?

I don't see why there's any need to open the backend at all, if it's
just appending data into an existing table!

John W. Vinson[MVP] You are correct. I do not need to open the back end file. I was looking for how others approached this problem hoping to create a resuable tool for the future. I wanted others ideas before making a final decision.

 

[dbahooker]

ROFL

so you just sit there and make the end user WAIT for 5 seconds while
you SYNC and relink and refresh?

ROFL


lose the training wheels; kids-- ADP rocks