- Jan 6, 2002
- 23,124
- 1,274
- 126
I had posted about this a while back, maybe 6 months, I cannot find that threat - because I suck lol. Here's the gist of things as they currently stand.
small business I do work for had a database built for them, the company they had do it is long gone and can't be found. And of course, I cannot get into the design mode to change it because it's locked down. Basically, they have a label printer which they use to print labels. It's on one of the computers and shared as a network printer. Today I'm hooking up a new PC, I install Access 97, which is the only version of Access that can open it, I tried in 2007 and it said I didn't have the rights to modify the DB or something. When I tried to print a label it said "unable to print on printer //scott/DYMO (blah blah blah) now, there hasn't been a PC named Scott in this offer for YEARS. But something stuck in the DB is looking for that printer on his computer. There are 2 other PC's, neither have problems printing - well neither did. One today decided to start looking for thr same printer on Scott's PC.
Since the DB is locked I cannot set the default printer, when the error message pops up they can click on the options tab, select the printer and tell it to print, but it's a few steps and with all the printing they do that's a crappy work around.
I got what I thought was smart and named one of the PC's Scott and added a network printer dymo but that didn't work. I'm not sure who the hell made the DB for them, but it would seem they hard coded the Dymo LabelWriter 310 into it as the default printer, not sure if there's any way to re-direct it.
Sorry for the long post but this is stumping the hell out of me. I'm going to suggest they have a new DB built, but for now is there anything I can do tomorrow to get the printer to print? On all the PC's if I go into the printer properties I can print a test page fine so I know it technically works on all of them, just not in the DB when they need to print labels
small business I do work for had a database built for them, the company they had do it is long gone and can't be found. And of course, I cannot get into the design mode to change it because it's locked down. Basically, they have a label printer which they use to print labels. It's on one of the computers and shared as a network printer. Today I'm hooking up a new PC, I install Access 97, which is the only version of Access that can open it, I tried in 2007 and it said I didn't have the rights to modify the DB or something. When I tried to print a label it said "unable to print on printer //scott/DYMO (blah blah blah) now, there hasn't been a PC named Scott in this offer for YEARS. But something stuck in the DB is looking for that printer on his computer. There are 2 other PC's, neither have problems printing - well neither did. One today decided to start looking for thr same printer on Scott's PC.
Since the DB is locked I cannot set the default printer, when the error message pops up they can click on the options tab, select the printer and tell it to print, but it's a few steps and with all the printing they do that's a crappy work around.
I got what I thought was smart and named one of the PC's Scott and added a network printer dymo but that didn't work. I'm not sure who the hell made the DB for them, but it would seem they hard coded the Dymo LabelWriter 310 into it as the default printer, not sure if there's any way to re-direct it.
Sorry for the long post but this is stumping the hell out of me. I'm going to suggest they have a new DB built, but for now is there anything I can do tomorrow to get the printer to print? On all the PC's if I go into the printer properties I can print a test page fine so I know it technically works on all of them, just not in the DB when they need to print labels
Facebook
Twitter