swshurts

The 70's are calling and they want their 8086 and assembler back...

AI runs on GPU’s - 1000’s of them, perhaps 1,000,000’s of them. The difference is where the processing is occurring, not the kind of hardware.

I have been involved with software development since 1986. During that time frame, I have been a programmer/analyst, team leader, IT director, and acting CIO. I have interviewed and hired many candidates during that time frame. If you are a fresh (or relatively fresh) graduate from school, I could care …

That little update app in my toobar said after July 29th - pretty precise, huh???

I agree with pritaeas. The program's user must have been GRANT'ed EXECUTE permission. If you use a generic user to log in to the database, chances are that this is a new app and that the GRANT for the particular user was never run.

Try following this: http://windows.microsoft.com/en-us/windows/homegroup-help#homegroup-start-to-finish=windows-7&v1h=win81tab1&v2h=win7tab1 I have seen this issue before. As I was not a fan of Windows 8.x, I put Windows 7 on the offending machine and the problem went away; however, you can give the link a shot and should have better results...

I agree with desmondo - more info needed. However, I have run into an issue with my provider which is very similar to what you describe. In those cases, I have had to contact my provider and they send a reset signal from their end. My only guess as to …

rubberman is right. You can very typically use memory that is higher speed than that required by your laptop; however, it will only operate at the maximum buss speed of your computer.

You haven't included the area of code where the error is occurring. How is tblPatient defined? What kind of backend are you using? There is apparently some restriction or range limits defined somewhere you need to find.