Group Policy Object - Copy Database frontend from NAS WITH icon
-
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
but I need a copy of the file and not a shortcut because it's a database front end that many people will have open and are writing to simultaneously.
It's standard to use a shortcut for that. As a front end, it specifically can't be written to and has no need to be local. Once you execute the shortcut, the front end is loaded into RAM and that it's a single starting file has no effect.
-
@scottalanmiller said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
but I need a copy of the file and not a shortcut because it's a database front end that many people will have open and are writing to simultaneously.
It's standard to use a shortcut for that. As a front end, it specifically can't be written to and has no need to be local. Once you execute the shortcut, the front end is loaded into RAM and that it's a single starting file has no effect.
lol, I'm clearly not an Access guy.
So what you are saying is that I could have 100+ users, with both x64 and x32 front end versions open for a backend, and everything is going to be just fine. So I should go ahead and just make it a shortcut to the frontend on the NAS.
-
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@scottalanmiller said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
but I need a copy of the file and not a shortcut because it's a database front end that many people will have open and are writing to simultaneously.
It's standard to use a shortcut for that. As a front end, it specifically can't be written to and has no need to be local. Once you execute the shortcut, the front end is loaded into RAM and that it's a single starting file has no effect.
lol, I'm clearly not an Access guy.
So what you are saying is that I could have 100+ users, with both x64 and x32 front end versions open for a backend, and everything is going to be just fine. So I should go ahead and just make it a shortcut to the frontend on the NAS.
No, I'm saying that the issues you are mentioning are related to the DB backend and are unrelated to the shortcut or the front end. Access is not designed for multiple users, period. It has a bolt on "never meant for production" work around to allow a handful to use it at the same time with bad performance. About five users is the limit of Access to work well.
No matter where you run the front end from, it is the back end that matters. Running 1,000,000 users from a single front end file, accessing 1,000,000 back end files will work just fine. 100 unique front ends, accessing a single shared backend, is not fine. You are trying to do the latter from your description.
-
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
So I should go ahead and just make it a shortcut to the frontend on the NAS.
To the front end, yes. The front end is not related to your concerns and it is standard in every system like this to do shortcuts for this so that updates are easy and universal.
-
Access as a front end also does not imply what the back end is. I'm using the concerns that you mention to assume you mean using JetDB as your backend, which is a joke of a product and doesn't work properly for how Access tries to use it. However, as a front end, Access is a tool that works with things like SQL Server as a back end. So with that, yes, thousands of users using Access front ends to a single SQL Server back up will work just fine and the versions of Access (IA32 / AMD64) can be mixed because it's just the front end and all talks T-SQL just the same.
So yes, if you truly only mean Access as the front end and properly deploy it for production then you can have hundreds or thousands of users without any real problem.
-
I'd copy the DB file itself to some directory on the PC (say c:\DB) , not to the desktop directly. This way the file is on the local machine. Then create a shortcut the way you are used to, pointing to that local file you put somewhere else on the machine (again, maybe c:\DB).
-
Is your manual process working for 100+ users you have now?
-
But, rule of thumb, the moment Access moves from "one guy's personal tool" to "IT is deploying something", something is wrong. Access has no business being deployed anywhere, it's an office suite scale tool, like Excel. All design of Access is around one user or just a tiny team managed without IT's involvement. Once IT is involved, Access was the wrong tool and things are going to go egg shaped.
-
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
Is your manual process working for 100+ users you have now?
Yea, so we've been using this method for longer than I've been here, so at least 4 years. I was always told "you have to copy the Front End from the NAS to the desktop, if you create a shortcut to it, bad things happen".
@scottalanmiller - This is an Access Front End and Back End. It's something that is a shared design among many other similar organizations to mine across the United States. Some of which have ditched it for obvious reasons you've outlined. Hopefully we'll get away from it soon.
-
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
Is your manual process working for 100+ users you have now?
Yea, so we've been using this method for longer than I've been here, so at least 4 years. I was always told "you have to copy the Front End from the NAS to the desktop, if you create a shortcut to it, bad things happen".
I bet - because when you do that - the temp file for the DB is on the NAS - and every person who's using it at the same time is using the same temp file - and that's bad, definitely bad!
-
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@scottalanmiller - This is an Access Front End and Back End. It's something that is a shared design among many other similar organizations to mine across the United States. Some of which have ditched it for obvious reasons you've outlined. Hopefully we'll get away from it soon.
That's what I figured. But it's only the backend that is really an issue. Now, how the front end runs that way, I'm not sure, I thought Access had to be installed.
-
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
Is your manual process working for 100+ users you have now?
Yea, so we've been using this method for longer than I've been here, so at least 4 years. I was always told "you have to copy the Front End from the NAS to the desktop, if you create a shortcut to it, bad things happen".
I bet - because when you do that - the temp file for the DB is on the NAS - and every person who's using it at the same time is using the same temp file - and that's bad, definitely bad!
See now we're getting it, I don't know where I went wrong at, but this is what I was trying to say the whole time.
-
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
Is your manual process working for 100+ users you have now?
Yea, so we've been using this method for longer than I've been here, so at least 4 years. I was always told "you have to copy the Front End from the NAS to the desktop, if you create a shortcut to it, bad things happen".
I bet - because when you do that - the temp file for the DB is on the NAS - and every person who's using it at the same time is using the same temp file - and that's bad, definitely bad!
See now we're getting it, I don't know where I went wrong at, but this is what I was trying to say the whole time.
Just to be sure... are you sure it is the front end that you are copying and not the back end (or both?) Where is the shared DB reside that everything is pointing to?
-
@scottalanmiller said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
Is your manual process working for 100+ users you have now?
Yea, so we've been using this method for longer than I've been here, so at least 4 years. I was always told "you have to copy the Front End from the NAS to the desktop, if you create a shortcut to it, bad things happen".
I bet - because when you do that - the temp file for the DB is on the NAS - and every person who's using it at the same time is using the same temp file - and that's bad, definitely bad!
See now we're getting it, I don't know where I went wrong at, but this is what I was trying to say the whole time.
Just to be sure... are you sure it is the front end that you are copying and not the back end (or both?) Where is the shared DB reside that everything is pointing to?
We put the Back End on a Server Share. This is definitely the Front End.
-
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
Is your manual process working for 100+ users you have now?
Yea, so we've been using this method for longer than I've been here, so at least 4 years. I was always told "you have to copy the Front End from the NAS to the desktop, if you create a shortcut to it, bad things happen".
I bet - because when you do that - the temp file for the DB is on the NAS - and every person who's using it at the same time is using the same temp file - and that's bad, definitely bad!
See now we're getting it, I don't know where I went wrong at, but this is what I was trying to say the whole time.
So you solve the problem by placing the front end DB file to c:\DB\db.mdb, and create your shortcut to c:\DB\db.mdb with your custom ico file. problem solved.
-
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@scottalanmiller said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
Is your manual process working for 100+ users you have now?
Yea, so we've been using this method for longer than I've been here, so at least 4 years. I was always told "you have to copy the Front End from the NAS to the desktop, if you create a shortcut to it, bad things happen".
I bet - because when you do that - the temp file for the DB is on the NAS - and every person who's using it at the same time is using the same temp file - and that's bad, definitely bad!
See now we're getting it, I don't know where I went wrong at, but this is what I was trying to say the whole time.
Just to be sure... are you sure it is the front end that you are copying and not the back end (or both?) Where is the shared DB reside that everything is pointing to?
We put the Back End on a Server Share. This is definitely the Front End.
I'm with scott - I'm surprised it's Access on the backend and not having the same problem... there presumably would be a similar temp file for the backend part, and that would be shared by everyone logged in at the same time... i..e problems.. but, apparently someone figured a way around that.
-
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
Is your manual process working for 100+ users you have now?
Yea, so we've been using this method for longer than I've been here, so at least 4 years. I was always told "you have to copy the Front End from the NAS to the desktop, if you create a shortcut to it, bad things happen".
I bet - because when you do that - the temp file for the DB is on the NAS - and every person who's using it at the same time is using the same temp file - and that's bad, definitely bad!
See now we're getting it, I don't know where I went wrong at, but this is what I was trying to say the whole time.
So you solve the problem by placing the front end DB file to c:\DB\db.mdb, and create your shortcut to c:\DB\db.mdb with your custom ico file. problem solved.
MDB is the database (backend).
-
@scottalanmiller said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
Is your manual process working for 100+ users you have now?
Yea, so we've been using this method for longer than I've been here, so at least 4 years. I was always told "you have to copy the Front End from the NAS to the desktop, if you create a shortcut to it, bad things happen".
I bet - because when you do that - the temp file for the DB is on the NAS - and every person who's using it at the same time is using the same temp file - and that's bad, definitely bad!
See now we're getting it, I don't know where I went wrong at, but this is what I was trying to say the whole time.
So you solve the problem by placing the front end DB file to c:\DB\db.mdb, and create your shortcut to c:\DB\db.mdb with your custom ico file. problem solved.
MDB is the database (backend).
what other file types does Access use? I'm assuming he has two - the front one, and the back end one.
-
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
Is your manual process working for 100+ users you have now?
Yea, so we've been using this method for longer than I've been here, so at least 4 years. I was always told "you have to copy the Front End from the NAS to the desktop, if you create a shortcut to it, bad things happen".
I bet - because when you do that - the temp file for the DB is on the NAS - and every person who's using it at the same time is using the same temp file - and that's bad, definitely bad!
See now we're getting it, I don't know where I went wrong at, but this is what I was trying to say the whole time.
So you solve the problem by placing the front end DB file to c:\DB\db.mdb, and create your shortcut to c:\DB\db.mdb with your custom ico file. problem solved.
Hopefully .accdb, not .mdb. AccDB replaced MDB 13 years ago, lol.
-
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@scottalanmiller said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
Is your manual process working for 100+ users you have now?
Yea, so we've been using this method for longer than I've been here, so at least 4 years. I was always told "you have to copy the Front End from the NAS to the desktop, if you create a shortcut to it, bad things happen".
I bet - because when you do that - the temp file for the DB is on the NAS - and every person who's using it at the same time is using the same temp file - and that's bad, definitely bad!
See now we're getting it, I don't know where I went wrong at, but this is what I was trying to say the whole time.
So you solve the problem by placing the front end DB file to c:\DB\db.mdb, and create your shortcut to c:\DB\db.mdb with your custom ico file. problem solved.
MDB is the database (backend).
what other file types does Access use? I'm assuming he has two - the front one, and the back end one.
Ah, I see. If you split them, then the back end of the front end is incorrectly referred to as the front end file. It's a back end to the front end. See my note earlier about Access (the front end) needing to be installed.
This is not the front end being copied, it's a local back end used by the front end.
Yes, in that case, it's an AccDB file that needs to be copied, because it is a backend, that MS refers to as a front end file. Ugh.
Much like how Hyper-V's first virtual machine is named the physical. Argh.
