Multi-users, Citrix MDE’s and Splitting dbs Questions

[GreyHounds]

I have an access database. I can have it loaded onto a Citrix server so folks in three time zones in the US as well as London and Australia can access it.

There won’t be many users at one time – but there will be updates by multiple people at the same time. All the other db’s I have done have been for my own processes or single users.

The users will be updating data and I have a record lock on the tables so if by off chance two people access the same record at the same time from the same group – it shouldn’t let them both edit at once.

I have spent the afternoon reading a lot of posts here regarding multi-users and splitting the db and have found tons of really useful information.

My question is about adding the Citrix component. If I had a file server where I could store the backend of a split db and distribute the front end I would do that because is seems most common. But what about Citrix?

What would be the advantages?
Do I still need to split the database if it is on a Citrix server?
If I split the db do I make the front end an MDE?
Are there any pitfalls I need to worry about with Citrix?


Splitting - If i need to update the database somehow i need to make sure the data is intact - so if i have to make changes would i have the admin send both the fe and be? do i need to relink the tables if i just make changes to the fe?

I will not have access to the citrix server - it's admin'd in another office.

Any information or links to information would be truly appreciated.

Thanks much!

Muddling thru

 

[lameid]

I say always split. The FE objects are the ones that tend to corrupt files the most and the data is what changes the most... Splitting just makes it less likely you'll lose something you can't get out of your backup.

You only need to relink Access tables if the path changes (other backends are another matter)... In the case of Citrix or any other Terminal Server you links need to point to a path the server can see... At least I think that is how Citrix works. Check with your admin to see what paths Applications can see when used on the Citrix server.

You can use an MDE or not... Principly it is the same issue... Do you want the users to be able to get into the raw VBA and do you want the hassle of creating an MDE?

Since Access version... 2000? - Access started locking FE objects more so... I would recommend each user have their own copy of the FE on the server to accomodate concurrent users. Access 97 was more forgiving but also allowed one User to overwrite another's Object changes. Both suggest distributing the FE. You of course want it local to the server for Citrix.

Last time I worked with Citrix it was an NT4 environment with Access 97... Citrix still looked like Windows for Workgroups 3.11. Even then it was for only one remote user. I have covered everything I expect to be an issue but I have not really used it to know if there are any 'integration' issues. I would not expect any. The only issue I haven't mentioned is executing multiple instances of Access on the server... It is not a small program and depending on your database sizes, both FE and BE, it may eat up a lot of Server RAM per user. If you have a query that runs against 100's of MB of data and multiple users run it, you may slow down the server noticeably. That is the only thing that may surprise your Citrix admin in a very bad way. I suspect he won't like the FE solution for each user either.

 

[fidlstix]

Lameid,

Thank you for your response. This is great information.

I will split and speak with the admin about the path. I am a little nervous about this one as we are storing data here. All the other db's are for pulling data not storing them.

Thanks again - wish me luck!!!

Definitely Less Muddled!

L