HOw to makes access db be used by other country users?

[sunilvedula]

Hi All,

I have a created a db which if it can be used by other countries (offices of the same organisation) would be very effective. The workflow requires other people in other countries to act on the db which would in turn be acted on by the people i work from. There is a common network drive (shared drive) which can be used but that would comprimise the speed of the database. another suggestion was suggested was to place it in a server, create a web based interface and make the db as the back end and let users use the webinterface through the organisation official internet sites. I have no idea how to go about it. what programming skills would be required if i have to do it. And how do i do it and what costs would that incur? Please pass me all your valuable suggestions for me to the get the best solution.

 

[rommelgenlight]

if the database that you work on with is simultaneously work with other country users and there is a need for updated data immediately then you really need the internet but if not necessary, then you can provide copy of the database the you work on to other countries and get it back from them and just update the main database that you have in your country with the database from other countries.

 

[sunilvedula]

yes you are right saying that the updated data is to be required immediealty and that is what we are working at as that would decrease the time required to wait. We do have internet (our company has a dedicated connection). So can i paste the db in a folder and use it. Would it work or is there any othe workaround?

 

[Simon_MT]

Try a Terminal Server, each country's regional settings can be included in individual user profile. Only one BackEnd database is required with each user having a Front End included in their profile.

The Terminal Server is just delivering screen dumps to users, Access is local, the data is local although local printers can be set-up through the local desktop connection.

Simon

 

[darbid]

I have a created a db which if it can be used by other countries (offices of the same organisation) would be very effective.

You are going to find there are many different ways to solve your situation and many opinions on which is the best.

I found myself in a similar situation 6 months ago and I too was a beginner. I had a MDB that was split and I wanted people in Germany/China/Japan to use it. You will see very quickly that when you share the MDB back end /front end over a file server only that there are problems.

I found a dedicated server computer that had SQL Server 2000 on it and thus used that.

You will see that SQL SERVER has a number of free editions (with limitations) but you can download one and try it out. As I was a beginner I first put SQL SERVER on my computer and then tested it with my MDB front end. I then had two computers in a Home Network and I put SQL SERVER on one and my MDB on another to test. After learning how things worked I then used the work server and started the proper testing. (these are baby steps but I am not the administrator of the work server so I had to make sure I knew what I was doing)

I can highly recommend the book Microsoft Access Developers Guide to SQL Server (it is old but it is going to give you a great idea of how to start with Access and SQL SERVER) it deals with both MDB or ADP front ends.

I use a lot of stuff from the above book.

 

[rommelgenlight]

try this one. http://www.hansenonline.net/Access/index.html

 

[sunilvedula]

Hi Rommelgenlight,
i think the link helps me. i am still trying it out. Just another question. Do you think it is a good idea to split the db and try out the said things in the link?

Hi darbid,

I will buy that book and see how much it can help and thanq for ur suggestion.

Hi simon,

I have no clue what is a terminal sever. Maybe you can throw more light on it

 

[darbid]

Hi darbid,
I will buy that book and see how much it can help and thanq for ur suggestion.

I would probably not outlay for the book right away unless you are going to do an Access frontent SQL Server back end.

You have a lot of reading ahead of you as my suggestion is but one of many which you could do. This Forum and this general section has your question answered in many many different ways.

 

[sunilvedula]

Hi Darbid,

My requirements (i need to put in the business case ) are a web server, and possibley a web page desingner. Is that all i require or anything else that i would be requiring for me to host my db on the web or on our company internet. Also after i complete my requirmentns i will need to decide if i will stick access front end or how do i go about it. Because my database is ready for use in my office but i think they will be requirining it to be used across other countries. pls suggest.
Also when i tried using hason suggestion it was not allowing me to save any of my queries as html. It does not give me that option. Is it restricted only to access 97 or something like that since i am using access 2003?

 

[Simon_MT]

The beauty with a Terminal Server is thart you need to do virutally nothing to your database other than a Front enfd and Back End. I have looked at web based solutions and whilst I can write ASP and ASP.Net, it is not easy, the wizrads in access are underwhelming and never used.

I still like the Terminal Server route, it is so simple and easy to implement.

Simon

 

[darbid]

Hi Darbid,
My requirements (i need to put in the business case ) are a web server, and possibley a web page desingner. Is that all i require or anything else that i would be requiring for me to host my db on the web or on our company internet. Also after i complete my requirmentns i will need to decide if i will stick access front end or how do i go about it. Because my database is ready for use in my office but i think they will be requirining it to be used across other countries. pls suggest.
Also when i tried using hason suggestion it was not allowing me to save any of my queries as html. It does not give me that option. Is it restricted only to access 97 or something like that since i am using access 2003?

Please first understand that I am not an expert, I am just someone who has gone through the experience (I must admit many of the posts you see for me are questions in this forum) I am just trying to give back as best as possible.

With that the only one thing I can say that you should do is to read and understand the options that people give you. You will find both questions and answers in this forum and also many links to articles on this stuff.

Once again one possible solution or best put what I did when I had a MDB and wanted people in many countries to use it was put it on a file server with a split front end and back end. In one minute I worked out that a file server will not work for a split MDB for the people in the other countries. I have read that this type of set up works fine for a simple local (cabled) network though.

I then started to do the exploring that you are doing now and things like terminal server were suggested to me. The thing that helped me was that a server computer already existed and it was running SQL Server 2000 and I was allowed to add my tables to it. And thus for me I have a front end MDB/MDE which I distribute to all clients and they all link back to this server.

 

[sunilvedula]

Hi darbid,
I too come in the same league as you. Well i also found out a similar situation. I was doing my bit of research. If we have an SQL server then i can use the upsizing wizard to convert my mdb to sql and then distribute my mde to other people who will use it. I think it is the same solution that you suggested that worked for yu. If i am right please let me know as i am in the process of trying that out

 

[darbid]

Hi darbid,
I too come in the same league as you. Well i also found out a similar situation. I was doing my bit of research. If we have an SQL server then i can use the upsizing wizard to convert my mdb to sql and then distribute my mde to other people who will use it. I think it is the same solution that you suggested that worked for yu. If i am right please let me know as i am in the process of trying that out

Ok yes that is correct you will at some stage be able to use the upsizing wizard from Access to upsize at least your tables to sql server. The first thing you should do is work out your connection with the SQL Server. At first (I say this cause one again there are different options with different advantages) try to establish a DSN connection with ODBC.

IF you are going down this track now is the good time to buy that book cause it talks about connections and linking and how to do them. It also talks about whether you want to use ADP or MDB (i am assuming you already have a MDB so this may not be that interesting to you)