Please post the exact code you use to connect to a database (hide the username / password, of course). Someone will perhaps be able to offer a workaround if you give us at least some information... Perhaps you're connecting to a database remotely without any reason..?
Basically, you're getting no answers about your firewall problems because there is no answer to this. Firewalls are designed to stop people from accessing things they shouldn't. ;) So, disable the firewall, it's as simple as that. If you're not allowed to... well, then your problem is not something this group can solve. Talk to people responsible... I know, it's a pain. :) But think of it this way, security policies are there for a reason, even if they might seem annoying. Regards, Ales On Tuesday, December 18, 2012 7:57:00 PM UTC+1, Seelife wrote: > > Hi Ron, thanks for that info. We thought as much. It seems its the > firewall that is causing us so many problems. We can run our apps with no > problems on machines with fewer restrictions. Apart from modifying the > firewall rights (hard to do), any suggestions to work around them other > than placing the apps and running as a pure python from Unix etc (also hard > for us to arrange). > > > On Tuesday, December 18, 2012 4:24:58 PM UTC+1, Ron McOuat wrote: >> >> >> The error traceback is saying the connection to the database could not be >> opened. The problem should be in the model file that has >> >> db=DAL(.....), >> >> the first parameter is the connection information. If the database is on >> another machine and a firewall is in the way you won't have any ability to >> connect. If you can't work out what is wrong on that line then post the >> model file. >> > --
