Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Using Access within "Terminal Services"

Status
Not open for further replies.

NaoTriste

Programmer
Dec 17, 2002
29
GB
I am having trouble developing in Access 97, concurrently with another developer using 'Terminal Services', even though we are developing completely different areas of the system (different screens, different modules, etc).

"Terminal Services" is a piece of Microsoft software that allows you work remotely on a Server ( a bit like PC-Anywhere) but it allows multiple users to be logged in simultaneously.

When developing an Access 97 DB together with another person it keeps on geting corrupt due to 'Virtual Memory' problems.

Although we are, of course ,using the same Server's processing capabilities, there is no size problem so is this an Access problem rather than a "Terminal Services" problem " ?
Basically, has anyone worked using this kind of Environment and had (even better solved) this kind of problems ??
 
I haven't used Terminal Server (an ironically apt name, IMHO) for a few years, but I would shy away from using it during the "development" phase. Terminal Server, unless it's been evolved, allows a remote CPU to "run" an application, and a user who is "networked" to that CPU gets the output pushed down the network wire to his PC. In effect, it allows you to share applications by loading and running the code on ONE cpu, but viewing the results on multiple CPUs. Very mainframe-y.

Trouble is, the ONE version of Access thats running on the remote CPU, is having trouble keeping track of who's doing what to whom, and when, in your database file, which I assume is also being "shared".

Even though you both are working on separate components, Access is not sophisticated enough to handle all the check-in/check-out version control stuff (which is understandable).

I suggest that both of you get a copy of Access, run it on YOUR PC, and after you develop a form/module/query/table/macro or whatever, copy the new component out to the Terminal Server version of the database.

It's simply not designed for this kind of development.

Jim





Me? Ambivalent? Well, yes and no....
Another free Access forum:
More Access stuff at
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top