Front-End vs Back-End Question

[calvinle]

Hi,

I kind off confuse between how the front-end and back-end works.

I made a project and it's in accdb file which contains all table, form, modules, etc..

Now, I want to protect my code, so I Save Publish into an Accde file. That will be the version so all my user will be using.

Now, I need to upload that into our server, let's say:
\\server\\tool\tool.accde

Now, I have the choice to create a shortcut, and link the target URL to the link above, but I know that is not so proper for multi-user uses (am I wrong?). It's better for them to have a version on their own desktop isnt it?

So I searched and I have found the version of Bob Larson, and the modified version of TK, but I still not get through to understand their meaning of "Front-End", "Front-End Master", and "Back-End".

Now, I have 2 files. tool.accdb which is main version on my own desktop. I can modify everything on it. I have another one that I put on the server which is tool.accde

Can anyone guide me step by step on how to use the:
Access_Front-End_AutoUpdating_Utility by Bob Larson?

There is a documentation about it, but I don't get which one will be the Front-End, or Back-End. Should I save 2 version of front end on my desktop and called them, tool (master).accdb and tool_fe.accdb. Then once everything is done, then save the tool_fe.accdb into tool_fe.accde and dump it into the server? But how will the code recognize in which server the front-end is if I did not really setup where it was since the beginning?

Please help.

Thank you.

 

[RainLover]

The Front End holds the Code. The pretty stuff.

Each user has a copy on their C:\ Drive. They can be different. One version for Tradesmen and another for the accountant.

In both situations they share the same Data which resides on a separate Database. Back End.

The back End is located on the server where all can have access to it and share the information.

Hope this helps.

 

[calvinle]

If my front end does not have any table, but only linked table? So this will be useless?

My access database is mainly use for form, and less table because there is no data saved to it. It's use to manipulate another external application, so the form uses for it is Form and VBA for it.

There is no information to share in between the front end and back end.

I guess I would need a code to auto copy the accde from the server to their desktop when there is a new version ..

 

[essaytee]

If my front end does not have any table, but only linked table? So this will be useless?

My access database is mainly use for form, and less table because there is no data saved to it. It's use to manipulate another external application, so the form uses for it is Form and VBA for it.

There is no information to share in between the front end and back end.

I guess I would need a code to auto copy the accde from the server to their desktop when there is a new version ..

If I understand you correctly, you don't need to split the database into a back-end/front-end combination. I'm assuming the data tables are only there to support your application process in manipulating the external application, that is, the tables themselves will store different records. Or put another way, User A doesn't need to know what data User B is manipulating. Put another way, User B does not need to access records that User A created. If this is the case, then you only have to worry about the front-end.

Assuming the above, have you considered how you will handle updates. Even though the data is not central to all front-ends, it maybe easier to split them anyway. The back-end data file merely residing in the same directory as the front-end. When updating, you merely update the front-end and don't have to worry about each user's data files. Even if the back-end data files require updating, that can easily be done via your front-end on first running of your front-end after an update; existing data retained.

As regards how the process of automatically copying the front-end to users, I'd suggest you incorporate a versioning system. Upon start up of the front-end, it checks a file (text file maybe) which contains a version number. Hard-coded (I prefer) or recorded in a front-end table, is the version number of the front-end. If the user's version is less than the version number checked from the file, then go about updating the user's copy of the front-end.

Simple batch files (I use a batch file and vbs script) will be called which delete the user's copy and copies from the server the updated front-end.

Obviously, you need a server location where everyone has access for this to occur.

Sorry, I'm not familiar with the Bob Larson application.

 

[calvinle]

Exactly..!

There is no relation between the user A or user B.

In summary, you are right. Let's say I have a accdb which is my main programming database to change vba code, form, etc.. When my update is done, I will publish via accde, and upload that file into the server. When they open their file, it will validate the version then if different frok the one on the server, then it will rewrite on their desktop.

So that being said, I will have total 3 files?
1 which is my main accdb.
1 is main accde in server
1 is accde in server that load the startup (version comparing). This one will be the file they have on their desktop right.

Do you have reference fpr me to start off on this?

Thanks.

 

[RainLover]

A quick question.

Are we talking about updating the Front End, or the Data held by the database.

 

[calvinle]

Front end..

 

[RainLover]

I guess I would need a code to auto copy the accde from the server to their desktop when there is a new version

I have some code buried in my library which I can retrieve.

If you want it just ask. I can't stop and get it just now but I can later today.

 

[calvinle]

Sure please do. I will check if that will really help me on this matter.

Thanks a lot!

 

[essaytee]

Exactly..!

There is no relation between the user A or user B.

In summary, you are right. Let's say I have a accdb which is my main programming database to change vba code, form, etc.. When my update is done, I will publish via accde, and upload that file into the server. When they open their file, it will validate the version then if different frok the one on the server, then it will rewrite on their desktop.

So that being said, I will have total 3 files?
1 which is my main accdb.
1 is main accde in server
1 is accde in server that load the startup (version comparing). This one will be the file they have on their desktop right.

Do you have reference fpr me to start off on this?

Thanks.

No, only two files.

1. Your development file (accdb) (Source Code)
2. The compiled version (accde) which resides on the server (user's copy)​

The version file does not need to be an Access database, in some apps I simply utilise text files, with an entry similar to, [VERSION]=109, (remember the old .INI files).

Do you have reference fpr me to start off on this?

As per Rainlover, I haven't got anything handy right now, will post later.

 

[RainLover]

Calvinle

Before I do anything let me just confirm that I understand the situation correctly.

From time to time you have a new version of the front end that you want to distribute to your users without them knowing about it. That is they do nothing out of the norm.

How would it be if I created a Shortcut and placed it on your desktop.

Then when you click it, it opens the front end. Nothing special.

In the background what it is doing is checking to see if the Front End on the server has been updated. If it has it copies the new file over to the user's machine then opens the new version.

The user sees nothing as this should only take less than one second longer than normal. All they see is that they have an updated version and they just simply carry on as though nothing has happened.

For the Administrator there are one or two small steps that he must do.

That is it.

Is this what you want.?

 

[calvinle]

Yes thats exactly it.

Here is what i have done before:
1 accdb which is my main source
1 accde on the server (front end)

I right click and create a shortcut of the front end to my desktop and change the link to the front end on the server. By doing so, many user are using the one on the server at the same time which slows down the performance of it. As you mentionned, you can make a comparison of version on the server and if different than the old, it will copy the one from the server to their computer?

I would like that.

Thank you

 

[RainLover]

Sorry I am taking so long.

I had trouble finding what I wanted and realised that what I have is very complicated. It is for travellers wanthing to log into the current Data via Dropbox and also Admin staff who are working live.

On top of that there are other features.

I need to cut it down as much as possible. This is taking some time. It has been a long time since I opened this and it is playing up.

Still working. Get back when I can.

 

[calvinle]

But I have 1 question about this. Will the user mainly open from only 1 file to execute the accde or that file only copy the accde to the user desktop then they will have to open from it?

Thanks.

 

[RainLover]

But I have 1 question about this. Will the user mainly open from only 1 file to execute the accde or that file only copy the accde to the user desktop then they will have to open from it?

Thanks.

The same shortcut first checks if the latest version is employed. If not it installs it.

Where the latest version is already employed then it simply opens that file.

So the one shortcut updates or opens depending on what is required.

ONE ONLY Shortcut does it all.

I have had my share of problems tonight. It is pat 2:00AM so I am going to get back to it tomorrow.

Sorry for the delay. At least I have fixed some problems I did not know I had.

 

[jdraw]

PMFJI but this confuses me

I right click and create a shortcut of the front end to my desktop and change the link to the front end on the server. By doing so, many user are using the one on the server at the same time which slows down the performance of it.

For clarity, each user should have their own copy of the front end on his/her PC. They do not share a server based file. As Rain says, and I hope I'm quoting him correctly,
your front end on your machine checks a version number with a front end on a server. The front end on the server is the latest, authoritative version. If the version on your PC matches the "authoritative version", carry on -- all is well. If the version on your PC doesn't match the authoritative version, processes will take a copy of the authoritative version and place it on your PC. When the front end on your machine opens, it will check the version on your PC with the "authoritative version" on the server, and now the versions will match, and all is well.

 

[RainLover]

PMFJI but this confuses me


For clarity, each user should have their own copy of the front end on his/her PC. They do not share a server based file. As Rain says, and I hope I'm quoting him correctly,
your front end on your machine checks a version number with a front end on a server. The front end on the server is the latest, authoritative version. If the version on your PC matches the "authoritative version", carry on -- all is well. If the version on your PC doesn't match the authoritative version, processes will take a copy of the authoritative version and place it on your PC. When the front end on your machine opens, it will check the version on your PC with the "authoritative version" on the server, and now the versions will match, and all is well.

Your explanation is close enough to being 100% correct. However I do not test Databases I place a Text file there to write what you wish for future reference. If different then the update happens.

Simply opening and closing the Text file is enough to make it different from the other.

Again apologies for the delay. Sometimes other things take our minds away and our fingers too.

Aim to finish by mid night. It is 10:00 PM now. Down under time.

 

[RainLover]

What Version of Access are we using here.

It may put a spanner in the works a little but we can over come what comes along.

 

[calvinle]

Thanks for taking time for resolving my issue. Really appreciate!
I am using Access 2010.

Thanks

 

[RainLover]

Think about this problem.

!0 Workers with 4 out on the road.

Six can access the server no problem.

There other 4 have finished for the day and are staying in Motels. They want to know what went on during the day.

All office workers no problem as long as the server is up.

In my example I placed the Back End (Not ACDDE) in a DROPBOX folder. Now what is front and what's back. Best off not using acdde etc.

All office staff can access the server but the travelling workers cannot get a copy of the latest.

Solution is that we test the connection to the server and if ok then continue on regardless. (Read\Write) If the are in a Motel with Internet connection, we can only download the latest back end so we do that but make the file read only. Done automatically. They make no entries, just view. Upon their return they may add the details in at Head Office

This is all a lot more complicated than I remembered.

We should end up with a Menu in a colour of your choice rot Read Write and a different colour for those on the road with a different. You can if you wish change Fonts, Font Sizes, Font Colours etc. The header and be different to the body of the Form. And so it goes on and on.

I don't want to destroy this as it may be useful to others. It is the only version that I know of. Copy write belongs to ChrisO and Myself Rainlover. Do with it as you desire but please retain any Copy write statements.

This original is now 50 Mb. I still need to cut some things out without destroying it.

Anyway back to the drawing board. I will finish this as soon as I can