SQL Server Approach

I have an outside office that has access to our servers here at that main office. I tried to put an Access app I made that works great in the main office. All the tables are in a BE Access. When I put the FE on the satellite office it takes forever to open a form with a linked BE table. I am sure it is connectivity between the offices. That said I can do nothing about this at this time. So I thought maybe I would go to MS SQL Server. When I put the tables in the BE will that be any faster? Do I need to link to the BE on SQL Server? What is the best approach in a case like this?
LVL 1
JArndt42Asked:
Who is Participating?
 
Gustav BrockConnect With a Mentor CIOCommented:
You can set a terminal server at the main office, then let the users at the satellite office reach that via Remote Desktop.
Requires, of course, a terminal server, but zero changes on your application.

/gustav
0
 
BAKADYCommented:
Hi JArndt42,

you can use replications of your access database, this will use less network because it transfer just the modified data. ask explicit for how to create an access database replication.

Regards
0
 
BAKADYCommented:
PS. What about you question Q:28148977, do you got access to the ms sql server? is this access database the same?
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
JArndt42Author Commented:
Hello BAKADY. what if two people make changes to the same field to the same record?
0
 
JArndt42Author Commented:
I have the tables on MS SQL Server. I always had that. What I did not have was a connection to the AS400 in SQL Server. Still working on that.
0
 
BAKADYCommented:
what if two people make changes to the same field to the same record?
this problem happends if you have just one access file too, if 2 person open the same record at different workstations.
with replications they don't do that, each database hat a copy of the data changes are logged in background with a timestamp, you can sync manually this makes the replicated database can works offline. if some data get corrupted (differences) you will be notify.
Sync time could be longer as just the copy time between main and satellite office
0
 
JArndt42Author Commented:
will the users need to be logged off the database in order to synch? I ask because we have a well known customer database, ACT!, that works that way and That is one of the draw backs of the program.
0
 
BAKADYCommented:
ACT!??? ach scheiße!!!

i don't have good experiences with ACT!... 4 year ago i was working with the version 8 (because a Client), it was terrible...

can be you are from Germany??

About Access, mmmm yes, maybe...
0
 
JArndt42Author Commented:
LOL. You know exactly what I mean then. No I am in US. Oregon. Can you believe that software is so popular? Well then you understand what I DON'T want it to do.
0
 
BAKADYCommented:
how many people have use this at your satelite office?
it is posible to do more than one replication which sync to master, maybe one for user (if they are 3-5)

do you really need to ask again... maybe someone else has a better idea about the posiblities and capabilities of access database replications... i have used it just twice in my live...
ask about pros and contras... maybe you became a interesting answer...
0
 
JArndt42Author Commented:
There are five in the satellite office. Does that sound good?
0
 
BAKADYCommented:
i doesn't sound bad... but i recommend you to get more information about...
this time i'm a little bit stumped... but i think it could be posible...
if you try this make a copy and work with it around a week for test reasons, parallel to the original... one of the contras of access replication is that you cann't undo it.

Regards.
0
 
BitsqueezerCommented:
Hi,

I would also recommend to use a Terminal Server for remote workstations. Replication is an abandoned feature of older Access versions, not implemented in current versions anymore so this is not very future compatible. Replication would only make sense if you need to access the data in situations where absolutely no online connection can be made available.

SQL Server has a compact edition which is able to replicate with it's "big brother" so in case you need replication it would be probably better to implement a compact edition on the workstation and connect the frontend with this. I personally have never done a replication so I cannot tell you much more about that.

The other advantage of a Terminal Server is the better performance as this runs on the server itself which normally has a better performance as any workstation. We made such solution in our current project (Access FE/SQL Server BE) and it works even in very problematic locations with only 1MBit online connection speed (shared with x other services like Internet, VoIP and so on).

Cheers,

Christian
0
 
JArndt42Author Commented:
I spoke the IT department and he likes the idea of Terminal Server. Not too hip about the price tag for 5 users but much better than what we have now. Thank you.
0
 
Gustav BrockCIOCommented:
You are welcome!

/gustav
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.