Collins, Darryl
Darryl.Collins at anz.com
Sun Dec 13 16:59:23 CST 2009
"I found the surge protector was in fact plugged in--to itself " I have seen this a few times with powerboards as well... Nearly did it myself once ;) Thanks for sharing these stories, I can't speak for the list, but I always find them educational and entertaining. Cheers Darryl. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Klos, Susan Sent: Saturday, 12 December 2009 8:08 AM To: accessd at databaseadvisors.com Subject: [AccessD] A call to the helpdesk I am sure many of us have similar stories. The one that always comes to my mind was a call from a distraught user while I was on the help desk. She insisted that there was nothing on her screen when she started her omputer. Me: Is the screen (monitor) turned on? U: I don't know. Me: Is there a small light on anywhere? U: No. Me: Is the monitor plugged in? U: Yes, it is plugged into that thingy on the floor that has all the plugs in it. (I figured she was talking about the surge protector) Me: OK. Is the "thingy with the plugs in it" plugged in? U: Yes. At this point I was a bit confused so I went to the user's office to track down the problem. I found the surge protector was in fact plugged in--to itself. I discretely plugged it into the wall and fiddled a bit with the plugs to make a show of trying to figure it out. Then I turned on the computer and the monitor and voila! It worked. I suggested to her that if things don't start she be sure the plugs are securely plugged into the surge protector and that the surge protector is securely plugged intot he wall. Susan Klos Senior Database Analyst Florida Department of Education Evaluation and Reporting Office Phone: 850.245.0708 Fax: 850.245.0710 email: susan.klos at fldoe.org -----Original Message----- Message: 19 Date: Fri, 11 Dec 2009 15:29:00 +0100 From: "Gustav Brock" <Gustav at cactus.dk> Subject: [AccessD] A call to the helpdesk To: <accessd at databaseadvisors.com> Message-ID: <sb226552.078 at cactus.dk> Content-Type: text/plain; charset=US-ASCII Hi all Since we started business in 1993 we've had numerous not-so-straight calls from clients but none like this. First: Client is a bit special - running a medium sized centre for plants, garden and accessories with three cash lines. The current owners bought the site about three years ago from the original owners who had ran it since 2001. Most equipment and software was carried forward from their previous business established in 1998. That year they bought a complete setup from us with a Novell NetWare 4.11 server, IBM pcs with Win98 and an Access based ERP system heavily modified by us to handle all inventory, heavy duty label printing and POS functions including barcode scanners and cash receipts. All this to tell you that this is proven equipment which has ran business for 7 days a week excluding Christmas and New Year in 11 years. Further, the server was bought second hand - it was our own primary server from 1993 which means - hold your breath - that we are dealing with a 16 years old Micron clone with 486 processor and 32 MB of ram, also an Adaptec SCSI controller, a VGA board and a 3Com NIC and, of course, ISA bus. The power supply and the harddisk have been replaced once. Talk about value for money. The Access mdb are shared on the NetWare server as are the main laser printer. The pcs are for the cash lines, and one is for the back office where it also controls two serial attached heavy duty label printers printing water resistant labels. We haven't heard from the client for some years and believed they had trashed it all and bought something new. But no. Yesterday the phone rang and we had a little chit-chat. Then: Client: We have taken up fireworks as a product line and need to create a new product group for this to be able to print labels, but we can't get access to the system! Me: Access? You just open the sales module and create the product group. Then run the routines to bring it forward to the cash line. Pretty straight forward. C: We know. We have written down somewhere how to. But we can't get access. M: Well, do you get some kind of error message? C: Yes. It's something about printer server is down. M: OK. When do you see this message? When you log in? C: Log in? M: Yes, when you turn the machine on, after a while you login. It is a box labelled Novell. Did you see that? C: No. It is always on. M: OK, then perhaps you have lost the network connection to the server (comment: Very unlikely, but you seek for causes) M: Do you have access to the Internet? C: Oh, you better get my partner. I'm not so good with computers and so. M: OK. C: (The partner takes over) Yes we have access. (comment: Clients lie. Always put cross-checking questions). C: But we can't access that. M: (slightly confused). Oh. But please check the network cables. Is the machine connected? C: Yes, the cable runs to the box (comment: switch) besides the server. M: Do you see some lights flashing at the cable's connections? C: Yes. M: And the cash lines are operating? C: Yes. M: Fine. Then the server and the network is operating. M: We better establish a firm point. How about rebooting the machine? Just press Ctrl-Alt-Del. C: (pushes keys a couple of times) It doesn't react. M: It may have locked up completely. Turn it off and then on. C: (Turns it off, waits, turns it on) M: (After a little while) Well, what do you see on the screen. A Novell login? C: No, it displays the same. M: The same what? C: It looks like it has done all the time. Something about printer server is off. M: (At this point realising that the monitor is connected to the server, and now the error message suddenly makes sense) M: Oh my, you are looking at the wrong monitor. What about the monitor for the workstation? C: What monitor? M: (Now more than slightly confused) Well, you have a monitor for the workstation, right? C: There is only this one monitor here. M: OK. Then someone must have moved the monitor from the workstation to the server to watch the backup log. M: (An old monitor used to be attached to the server, and I thought it was now gone) M: Move it back to the workstation so it can tell us what is happening. C: (Connects the monitor to the workstation) M: What do you see? C: There is a message about post ... M: (Knowing that this means some kind of hardware change on an IBM) It has detected some change in hardware. Just press F1 to continue. C: (Pressing some keys) Nothing happens. M: Strange. Are you sure the keyboard is connected? Does the Caps and Num lock work? C: Yes, I can turn them on and off. That's all. M: (Now realising the impossible) Please check the keyboard cable. Where is it connected please? C: (Fumbling with cables) It runs to the server ... M: OK. That explains. The keyboard has been moved to the server too. Please move it to the workstation. C: The plug doesn't fit! M: (Suddenly remembering that old keyboards had a DIN plug and not a PS/2 plug) M: The keyboard and the monitor are those intended to be used with the server, I guess. Do they look pretty old? C: Yes. M: OK. Both the monitor and the keyboard are those for the server. M: Where are the keyboard and monitor for the workstation? Has someone disconnected those? M: (comment: At this point the partner had left the room) C: I don't know. There are no more monitors or keyboards in the office (comment: office is pretty small and easy to glance) M: But how do you operate the workstation? Don't you use it for printing the thick labels? C: Yes we do. Don't know where the monitor has gone. (He yells the partner with no success). M: OK. You better talk to your partner and ask where he has taken the monitor and keyboard. C: I'll do that. M: Fine. And when you have attached these, if you still have a problem, please call again. C: Yes. Thanks! (hangs up) The client didn't call back. Once again, the people working full time at the helpdesks around deserve the deepest respect. I know for sure I wouldn't have the patience needed. /gustav ------------------------------ Message: 20 Date: Fri, 11 Dec 2009 10:24:41 -0500 From: jwcolby <jwcolby at colbyconsulting.com> Subject: Re: [AccessD] SPAM-LOW: A call to the helpdesk To: Access Developers discussion and problem solving <accessd at databaseadvisors.com> Message-ID: <4B226439.20602 at colbyconsulting.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed ROTFL. It takes a certain type of personality. Or good drugs. I didn't say that. That was a flashback. Oh noooooo I'm seeing colors... ;) John W. Colby www.ColbyConsulting.com Gustav Brock wrote: > Hi all > > Since we started business in 1993 we've had numerous not-so-straight calls from clients but none like this. > > First: Client is a bit special - running a medium sized centre for plants, garden and accessories with three cash lines. The current owners bought the site about three years ago from the original owners who had ran it since 2001. Most equipment and software was carried forward from their previous business established in 1998. That year they bought a complete setup from us with a Novell NetWare 4.11 server, IBM pcs with Win98 and an Access based ERP system heavily modified by us to handle all inventory, heavy duty label printing and POS functions including barcode scanners and cash receipts. > All this to tell you that this is proven equipment which has ran business for 7 days a week excluding Christmas and New Year in 11 years. Further, the server was bought second hand - it was our own primary server from 1993 which means - hold your breath - that we are dealing with a 16 years old Micron clone with 486 processor and 32 MB of ram, also an Adaptec SCSI controller, a VGA board and a 3Com NIC and, of course, ISA bus. The power supply and the harddisk have been replaced once. Talk about value for money. > The Access mdb are shared on the NetWare server as are the main laser printer. The pcs are for the cash lines, and one is for the back office where it also controls two serial attached heavy duty label printers printing water resistant labels. > > We haven't heard from the client for some years and believed they had trashed it all and bought something new. But no. Yesterday the phone rang and we had a little chit-chat. Then: > > Client: We have taken up fireworks as a product line and need to create a new product group for this to be able to print labels, but we can't get access to the system! > Me: Access? You just open the sales module and create the product group. Then run the routines to bring it forward to the cash line. Pretty straight forward. > > C: We know. We have written down somewhere how to. But we can't get access. > M: Well, do you get some kind of error message? > > C: Yes. It's something about printer server is down. > M: OK. When do you see this message? When you log in? > > C: Log in? > M: Yes, when you turn the machine on, after a while you login. It is a box labelled Novell. Did you see that? > > C: No. It is always on. > M: OK, then perhaps you have lost the network connection to the server (comment: Very unlikely, but you seek for causes) > M: Do you have access to the Internet? > > C: Oh, you better get my partner. I'm not so good with computers and so. > M: OK. > > C: (The partner takes over) Yes we have access. (comment: Clients lie. Always put cross-checking questions). > C: But we can't access that. > M: (slightly confused). Oh. But please check the network cables. Is the machine connected? > > C: Yes, the cable runs to the box (comment: switch) besides the server. > M: Do you see some lights flashing at the cable's connections? > > C: Yes. > M: And the cash lines are operating? > > C: Yes. > M: Fine. Then the server and the network is operating. > M: We better establish a firm point. How about rebooting the machine? Just press Ctrl-Alt-Del. > > C: (pushes keys a couple of times) It doesn't react. > M: It may have locked up completely. Turn it off and then on. > > C: (Turns it off, waits, turns it on) > M: (After a little while) Well, what do you see on the screen. A Novell login? > > C: No, it displays the same. > M: The same what? > > C: It looks like it has done all the time. Something about printer server is off. > M: (At this point realising that the monitor is connected to the server, and now the error message suddenly makes sense) > M: Oh my, you are looking at the wrong monitor. What about the monitor for the workstation? > > C: What monitor? > M: (Now more than slightly confused) Well, you have a monitor for the workstation, right? > > C: There is only this one monitor here. > M: OK. Then someone must have moved the monitor from the workstation to the server to watch the backup log. > M: (An old monitor used to be attached to the server, and I thought it was now gone) > M: Move it back to the workstation so it can tell us what is happening. > > C: (Connects the monitor to the workstation) > M: What do you see? > > C: There is a message about post ... > M: (Knowing that this means some kind of hardware change on an IBM) It has detected some change in hardware. Just press F1 to continue. > > C: (Pressing some keys) Nothing happens. > M: Strange. Are you sure the keyboard is connected? Does the Caps and Num lock work? > > C: Yes, I can turn them on and off. That's all. > M: (Now realising the impossible) Please check the keyboard cable. Where is it connected please? > > C: (Fumbling with cables) It runs to the server ... > M: OK. That explains. The keyboard has been moved to the server too. Please move it to the workstation. > > C: The plug doesn't fit! > M: (Suddenly remembering that old keyboards had a DIN plug and not a PS/2 plug) > M: The keyboard and the monitor are those intended to be used with the server, I guess. Do they look pretty old? > > C: Yes. > M: OK. Both the monitor and the keyboard are those for the server. > M: Where are the keyboard and monitor for the workstation? Has someone disconnected those? > M: (comment: At this point the partner had left the room) > > C: I don't know. There are no more monitors or keyboards in the office (comment: office is pretty small and easy to glance) > M: But how do you operate the workstation? Don't you use it for printing the thick labels? > > C: Yes we do. Don't know where the monitor has gone. (He yells the partner with no success). > M: OK. You better talk to your partner and ask where he has taken the monitor and keyboard. > > C: I'll do that. > M: Fine. And when you have attached these, if you still have a problem, please call again. > C: Yes. Thanks! (hangs up) > > The client didn't call back. > Once again, the people working full time at the helpdesks around deserve the deepest respect. I know for sure I wouldn't have the patience needed. > > /gustav > > ------------------------------ Message: 21 Date: Fri, 11 Dec 2009 10:50:04 -0500 From: "Reuben Cummings" <accessd at gfconsultants.com> Subject: Re: [AccessD] Rounding Error - A2K To: "'Access Developers discussion and problem solving'" <accessd at databaseadvisors.com> Message-ID: <57BAA4FB78414D96AAA6C5D59FC80B03 at reubennx9500> Content-Type: text/plain; charset="us-ascii" Nope. Just did it again and you're right. Yours works fine. I must have misplaced something when I was trying it Wednesday night. Sorry. Thanks, Gustav. Reuben Cummings GFC, LLC 812.523.1017 > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav > Brock > Sent: Thursday, December 10, 2009 8:45 AM > To: accessd at databaseadvisors.com > Subject: Re: [AccessD] Rounding Error - A2K > > > Hi Reuben > > I did some tests with no errors and returning the correct data type. > Are you sure about this? > > /gustav > > > >>> accessd at gfconsultants.com 10-12-2009 12:57 >>> > Thanks. That appears to work. However, I think your paranthesis are > off. > For anyone wanting this for future use I had to change it to... > > > CurResult = CCur((CurAmount * CCur(100 * SngPercentage))/ 100) > > Only added two paranthesis (to completely inclose the multiplication > part), but it makes sure the math gets done before it gets divided by > 100. > > Thanks for the help. > > Reuben Cummings > GFC, LLC > 812.523.1017 > > > > -----Original Message----- > > From: accessd-bounces at databaseadvisors.com > > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav > > Brock > > Sent: Thursday, December 10, 2009 4:18 AM > > To: accessd at databaseadvisors.com > > Subject: Re: [AccessD] Rounding Error - A2K > > > > > > Hi Reuben > > > > There is your explanation: cur * sng returns a double. > > > > What you could do is to keep storing the percentage as a single. > > When using it for calculation, do: > > > > CurResult = CCur(CurAmount * CCur(100 * SngPercentage) / 100) > > > > This will calculate using your six decimals and (with CCur) round > > the result to four decimals. > > > > /gustav > > > > > > >>> accessd at gfconsultants.com 10-12-2009 03:16 >>> > > Stuart and Charlotte, I'll play with the single/double issue. > > > > The dollar amounts are all currency. > > > > The percentage (.25xxx) is a single. Not sure why as this is the > > first time I've ever used a single. > > All these years and I've never used single and the first time I do > > it BITES me. > > I wanted to use currency for the percentage, but the state defines > > these rates to 6 decimals. > > > > Reuben Cummings > > GFC, LLC > > 812.523.1017 > > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > ------------------------------ Message: 22 Date: Fri, 11 Dec 2009 11:13:15 -0500 From: "Susan Harkins" <ssharkins at gmail.com> Subject: [AccessD] Another article you might want to take part in To: <AccessD at databaseadvisors.com> Message-ID: <332033CB1E684498ADD7617B6AC33B2A at SusanOne> Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original I'm writing about the Access features/tips... whatever that we forget about -- they work great, but we forget to use them, usually because we don't use them all the time. If you have something you want to add, I'll give you credit and a link in the article. Susan H. ------------------------------ _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd End of AccessD Digest, Vol 82, Issue 13 *************************************** -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com "This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ National Bank Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."