front end database

[mhisma]

Dear forums,
kindly need some suggestions,
I have a mdb file that has been splitted into front end and the back end for multi user database purpose. front_end contains a form named INPUT that will be shared to the other team member by locating it on the network drive ( M: for example).
I put the front_end and the back_end on folder M:\DATA\ for example, and then I make a copy of the front_end and I put it on folder M:\DATA\FRONT_END, this folder will be copied by another team member and then paste it on their local, for example in C:\MHISMA\.
Problem appears when users trying to open the mdb that has been copied into their local ( no access installed on their machine, they just installed access runtime instead), the INPUT form did not appear
Why should I do so INPUT can be opened and used by other user on their own local?
Many thanks for the help, I am totally drew a blank on this

 

[Rachael]

What version of access are you running, maybe the other machine hasn't had the content enabled ie you have to set the folder as a trusted site for the code to run, this might be what is stopping the INPUT from being opened

 

[mhisma]

I am running Access 2003, the other did not install Access on their PC, they just install
Access runtime. Can we use Access runtime to view splitted database?

 

[Rachael]

Shouldn't be a problem at all using runtime with split databases, are you sure the back-end path on the runtime machine is correct because a database using runtime won't tell you what's going on and why things are failing

 

[boblarson]

I am running Access 2003, the other did not install Access on their PC, they just install
Access runtime. Can we use Access runtime to view splitted database?

How is the form being opened? Is it set to open automatically by setting the startup options? You have to have it open the form because when you run the runtime version of Access you do not get the database window so you can't select objects from it.

 

[mhisma]

No, the copied front_end mdb is double clicked in the local drive,OK, I understand now why nothing happened when the copied mdb is double clicked by the user.
Would you like to advise how to deal with this problem?

 

[boblarson]

No, the copied front_end mdb is double clicked in the local drive,OK, I understand now why nothing happened when the copied mdb is double clicked by the user.
Would you like to advise how to deal with this problem?

On the machine that has Access installed, open the database and go to TOOLS > STARTUP and then up in the top right find DISPLAY FORM/PAGE and select the form you want to open when the database is opened. Then close the database and that should be set now for the runtime user.

 

[mhisma]

OK,it works well
great thanks for the assistance

 

[boblarson]

OK,it works well
great thanks for the assistance

Glad we could help

 

[mhisma]

updating front_end

I am sorry for not remembering it before,
the form consist of two part, the input part and properties data part. The properties data part is not static data,it may change daily and its source are several ODBC database ( linked to access application )
how can people with access runtime refresh those properties data?

 

[boblarson]

I guess I'm confused as to how the properties data part is being updated. How is that happening? What is the process and how do you currently have it set.

 

[mhisma]

For example,
I build a form to input the result of an oil well reviewing in a team meeting. So my form consists of
1. Combo box named OIL WELL contains list of oil well name in an oil field
2. Text box named PRODUCTION which containing last production of this oil well
3. Text form ( memo ) named RESULT to input the result of team meeting
The OIL_WELL and PRODUCTION are linked to a fixed table named LAST_STATUS which is also linked to an external ODBC table named LAST_PROD, LAST_PROD is refreshed daily. I develop a query named UPDATE_LAST_STATUS so when I run the query, LAST_STATUS will retrieve the most updated data of an oil well from LAST_PROD. When data is refreshed, then we input the meeting result on RESULT then save the form to a fixed table named REVIEW_RESULT
Since the access runtime user can't run the query, what should I do to ensure other user will get the latest data on their form. Am I able to refresh the mdb which has been located on other team local drive?

 

[boblarson]

Since the access runtime user can't run the query, what should I do to ensure other user will get the latest data on their form. Am I able to refresh the mdb which has been located on other team local drive?

Put a button on the form that runs the query. The runtime user can run a query, but you have to give them a way to open it.

 

[mhisma]

Thanks for the nice advise and assistance

 

[boblarson]

Thanks for the nice advise and assistance

Glad that we could help you out. (and welcome to the forum by the way)

 

[mhisma]

Dear forum,
the given advise has worked so well but I still need some advise about how to handle this.
I've put a command button on the form that will run UPDATE_LAST_STATUS automatically, it worked fine when I copy the FE and paste it on my own C:\
drive but when i copy the FE and paste it on the C:\ drive on other user, I found it don't work with the reason "ODBC connection to [user data sources name] failed". Fyi, the two user ( An user and I ) have different user data source name.
What should I do to make other user can run the query from their local drive? Are we have to have the same name of ODBC user data source?

 

[boblarson]

What should I do to make other user can run the query from their local drive? Are we have to have the same name of ODBC user data source?

Yes, you both must have the SAME exact ODBC user data source.