So we have our datapage database installed on local drive....and in this day and age, everyone has their own network login credentials. This is creating problems with our datapage use. If Im logged on and running parts and then log off for the nightshift guy to come in....and he logs in on his account........Datapage is not showing the parts that I ran and vice versa. We are using the same Datapage login (Default administrator) and we both have full local admin rights on each of our accounts.
How can we make this work. Obviously for privacy and business ethics, I cant just leave my login up for him. I really dont understand, if we are using the same database.....why arent the parts showing up. Why would it make a difference who is logged on.
This aint exactly working out well for PCDMIS either.
It sounds like you are both sending data to a different database, and DataPage is looking at your separate databases. I've had 5 unique logins, on the CMM computers, and the DP computer, and haven't had the issue you are having.
Ok, you are right....when my nightshift guy starts a program and turns stats on......his PCDMIS does not have the database name that I am using available in the drop down menu. Nor was Datapage on his logon pointing to the correct database, he was using the default demo database.
Now the question is.....how can I get his PCDMIS logon to point to that directory. Ive fumbled around a bit and have had no luck. I see where to change the option in datapage itself to the correct database though.
Datapage seat is on my office computer. As for the operator log in. We use a special restricted shop user profile that has the admin rights present but hidden from operator access. They run pc-dmis in protected mode, and I can go use the same computer and profile, and create new programs at the machine with no issues. This way, we don't have to maintain and control many different log ins with the same permissions to keep track of.
Operators don't use Datapage, they just run parts.
Call IT, have them make a DNS for through ODBC that points to that Database. A DNS needs to be created with the same name for every users that logs in.
I apologize, they need to create a "DSN" not and "DNS". One is created for the working users in ODBC they should be able to look at that and replicate it. As far as alternatives, if you want him to have the same drop down as you, no there is not.
Ok we have gotten to the point where we can now find the database on both logins. But when logged onto the secondary user account and selecting the PCDMIS stats command and we try and test the connection, this is the error we are getting (attached).
Even though all the stats commands and datapage settings all point to one database......its still sending stats over to the demo datbase on the secondary login account.
Honestly it looks like the DSN is not setup correct, they probably forgot to change the default database to your datapage database and are trying to write to the master database That's an SQL error telling me there isn't a table for the part name.