@Zecc said:
Nah, the problem is reverse-engineering the code to find out if the salaries are stored in tblEmploieesInfo002.cColumn028 or in employess.colTextVariable69.
If only they would have put it in tblSalariesTable.fldSalaryField
@Zecc said:
Nah, the problem is reverse-engineering the code to find out if the salaries are stored in tblEmploieesInfo002.cColumn028 or in employess.colTextVariable69.
If only they would have put it in tblSalariesTable.fldSalaryField
@morbiuswilters said:
Wow, how very mature of you. We are all impressed with your awesome abilities.
Thank you. It's always a pleasure to know I've impressed some random guy on the internet.
I used to receive a lot of hardware, both new and replacement parts, from Dell. This was almost always over packaged, although not to this level. We had an agreement to keep any dead hard drives for destruction, but were constantly receiving the prepaid shipping labels to return them. I was also a bit bored.
Being as I was in possession of a lot of large boxes, prepaid shipping labels, and extra time, Dell received a lot of items they probably didn't want. Broken, decade old CRT's. Empty pizza boxes. Joke e-mails from the spam folder. Autographed take out menus. An entire box fan, disassembled and spread across 2 or 3 boxes. Broken parts left on my parts shelf from Non-Dell machines. Furniture, again disassembled and spread amongst multiple boxes. Leftover Halloween candy. Coupons. Shredded newspaper. Comics section of Newspaper. Half completed crossword puzzles. Flowers. Mostly empty boxes of office supplies. Origami/Paper Airplanes. Crayon drawings of the hard drives. Books on NT3.51. Voltron Stickers. Green plastic army men. Unopened bags of chips. Burger King game peices. Serial mice. Other boxes.
My email address was associated with most of it, and I never received any questions or comments. Interestingly enough, should I fail to ship them something, I'd get a call/email about the hard drive I failed to return, which would result in me digging up the "Keep your Hard Drive" documentation. Should I ship them an empty pizza box, no call came. Should give you some insight as to the tracking methods used. Note that this was a few years ago, and they may have changed.
I always wondered if the parts return department was amused or annoyed by my antics. Perhaps a bit of both, depending on what I sent that day.
I might be completely off base here, but you did mention that you have to coordinate IP Addresses. From that, it seems unlikely that any sort of DHCP server was running. If that assumption is correct, this scenario may have been an attempt to gather data to setup DHCP reasonably intelligently, and remove the burden of coordinating IP addresses. Under some conditions, it makes sense for servers to have IP addresses reserved in the DHCP scope; netting you the advantage of a "static" IP address for your server, as well as the ease of maintenance of DHCP should you have to change, for example, your DNS settings.
Many of the SysAdmins I've worked with assume that any "server" requires a static IP address, and that anything running 2003/2008/etc was a server, while anything running XP/etc was not.If it was for a firewall, I'd expect them to want a list of require protocols as well- A SMTP Server, Web Server, and FTP Server all have very different firewall requirements.
If it was for licensing, they'd want the version of the OS. Of course, if it was for a DHCP Server, and I was running the show, I'd also like the IP addresses of any network printers, and for you to do the work of collecting the MAC Address. Given the IP, of course I could do myself; probably have the script to add the information to the DHCP Server lookup the MAC address when it did the addition, assuming the server was on. But I'd rather not have to.