Access on thin client?
Can Access run on a thin client ? If so, how?
The company is running Windows Server 2012R2.
thank you
respectfully,
crystal
The company is running Windows Server 2012R2.
thank you
respectfully,
crystal
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thank you, Pat. Of course, it is best for each to have their own front-end (each FE has a setup program that stores who they are in a database property). First I have to figure out how to get them to run Access!
There are about 10 thin clients in a manufacturing facility that are currently tracking to a web program, which is going to be replaced with an Access program I have already written.
Obviously the thin clients are already connected somehow ... how do I find out what is being done? (or should I ask another question about that?) IT is outsourced, which is another problem and hopefully they will get someone in-house but that person will probably need to be trained.
There are 2 BEs: one is Access and the other is SQL Server.
There are about 10 thin clients in a manufacturing facility that are currently tracking to a web program, which is going to be replaced with an Access program I have already written.
Obviously the thin clients are already connected somehow ... how do I find out what is being done? (or should I ask another question about that?) IT is outsourced, which is another problem and hopefully they will get someone in-house but that person will probably need to be trained.
There are 2 BEs: one is Access and the other is SQL Server.
Hi Crystal,
Did you create an Access web app? If not, the thin client won't be able to run it. You will need to use Citrix or maybe TS so the app can run in a browser. I don't know how you could tell what the thin clients are connected to. Your client must have had some plan if he hired you to develop an Access app.
Pat
Did you create an Access web app? If not, the thin client won't be able to run it. You will need to use Citrix or maybe TS so the app can run in a browser. I don't know how you could tell what the thin clients are connected to. Your client must have had some plan if he hired you to develop an Access app.
Pat
ASKER
thanks, Pat. I got hired because of a client I did work for about 10 years ago recommended me (he is still using the application I wrote to schedule jobs to optimize changing bits on a router). I have written other things for them that they are using. The web service being used to capture data on job tracking through its stage refuses to share that data back to the company so now I am looking at replacing that application too since internal applications need to know where a job is. That data needs to be integrated.
I considered a web app -- but they can't do that much, not that the machines need that much. The desktop application could link to those tables but because of the way web apps are designed with SharePoint, I am not sure they could run them either without doing something that would also let desktop Access work, which is preferable anyway.
I considered a web app -- but they can't do that much, not that the machines need that much. The desktop application could link to those tables but because of the way web apps are designed with SharePoint, I am not sure they could run them either without doing something that would also let desktop Access work, which is preferable anyway.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thank you, gustav. I read that article and plan to read the rest of them too!
Pat, I feel the same way. I read the service agreement but nowhere does it say they can have their own data, just that the data will be deleted if they don't continue paying.
thanks, Jim. That makes sense.
If IT was internal, they would realize what the company needed and offer suggestions. Everything is done via work ticket and what is wanted must be specified so, as you can probably imagine, what ends up happening is not necessarily what is really needed.
This is new territory for me. It is important that I ask the company to ask IT for the right things, so I need to learn exactly what that is.
Pat, I feel the same way. I read the service agreement but nowhere does it say they can have their own data, just that the data will be deleted if they don't continue paying.
thanks, Jim. That makes sense.
If IT was internal, they would realize what the company needed and offer suggestions. Everything is done via work ticket and what is wanted must be specified so, as you can probably imagine, what ends up happening is not necessarily what is really needed.
This is new territory for me. It is important that I ask the company to ask IT for the right things, so I need to learn exactly what that is.
ASKER
thank you all for sharing your thoughts and giving me ideas
for Access 2013, the minimum requirement is 1Ghz processsor with SSE2 instruction set, 1GB RAM for 32-bit and 2GB RAM for 64-bit and minimum 3GB free space.
the only concern is network performance if all drives are network based shares, as Access is a file based database system, file system performance is critical for Access.