Conceptually: Updating Modules/Code remotely?

[tweedle]

So I have a client where I've built them a client/server db for some analysis.
As changes are requested and coded, I'm delivering new versions of both DB objects via web shared files. In doing so, each time the dbs are delivered, I'm stripping the data for a complete rebuild which is getting time-consuming. They just pull them down and scheduled services take care of the rest.

Is there a method I can build in that would allow the existing c/s DB to scan a known directory & import .bas modules?
Essentially a version/code manager built into the DB.
They're not real trainable for getting into IDE; even to import a bas module, and I suspect something like this is on the edge of allowable Office security protocols.

Anyone seen this done?

Appreciate your input.
Office 2007 .accdb

 

[Norie]

I don't know too much about client/server database situations.

If this was a stand-alone database then the first thing would probably be to split it into a front-end/back-end.

The back-end would hold all the data and the front-end would have all the code and I suppose could be regarded as a UI.

If there was a change in the front-end all you would need to do would be to replace it with the newer version.

One advantage of this approach is that the data and code are separate which decrease the chances of data loss due to corruption.

Couldn't this approach or something similar work with a client/server setup? Or am I totally missing the target.

Mind you I am a little confused by what you actually want to do, especially the mention of importing code/bas files.

That probably is possible but I would think it might be a kind of last resort.

One issue that method raises is security which I would imagine would be a major consideration in a client/server environment.

 

[tweedle]

The DB is, well was, split into Front and Back, then the request came to take their data with them on their laptops. So the Front end carries the data too.
I'm trying to figure if I can programmatically update the BAS code without any more user intervention than dropping the BAS file in a directory.

The Front End now carries data with it, so the replace method is getting cumbersome and what I'm trying to mininmize.

Security for the client's perspective is not a great concern - it's hacking my way through Office security that has me questioning feasability of my concept.

Rough Picture: 
-----------------
| hosted SQL Svr |
-----------------
      |
      |
-------------
| DB-Data    | My Part 1 (translates and cube-builder)
| (server)       BAS code here
------------- 
      |
      |
--------------
| DB UI+Data | My Part 2 (Data+Queries+User Queries+Graphs)
| (client)         BAS code here
--------------

 

[Norie]

What's stopping them having a front-end/back-end setup on their laptops?

Why would they need/want the two combined?

Isn't there a possibility of data going out of sync?

eg data is updated/changed/delete on laptop but the changes aren't carried over

Or is that being dealt with elsewhere?

Or am I again totally missing something?

 

[tweedle]

It's strictly reporting, i.e. one way feeds to the lap tops.
I track the updates for the various clients, so I know what data to update.