I am one 2.5 user, too.
Reason is, that thanks to 4Suite (which is a fantastic XML framework) we are
bound to 2.5.
I didn't find a better XML framework for Python but it's not gonna developed
further and will not be
ported to 3.x (reminds me of contacting Jeremy Kloth for a port to a newer
Pytho
On Mon, Apr 20, 2015 at 7:49 AM, Niemann, Hartmut <
hartmut.niem...@siemens.com> wrote:
> [...]
>
> Is this the best way to access an mdb database from python (2.7) or what
> would
>
> be preferred?
>
>
>
Rather than programming ADO by COM interface, you might find it easier or
more convenient to
I also cannot read German, and also I guess that you do not have the
correct provider. There are numerous difficulties with 64 vs 32 bit
providers for Access (Jet) databases.
More information about providers can be found on the links in
http://adodbapi.sourceforge.net/quick_reference.pdf
I in re
Blair Hall wrote:
>
>
>
> One ugly alternative would be to edit sys.path in your code before you
> start your imports. If you remove everything but the Windows
> directories, that should solve the problem.
>
>
> I don't follow. Surely sys.path has nothing to do with it? It is the
> Loa
On 04/20/2015 9:49 AM, Niemann, Hartmut wrote:
this is the source
try:
print "Open ADOB.Connection"
ado = win32com.client.Dispatch("ADODB.Connection")
connectionstring = "Provider=Microsoft.Jet.OLEDB.4.0; Data
Source=\"%s\"" % filename # A
Hello!
I try to open and write an (Access 2000) mdb file, and get an error I cannot
interpret.
This code as worked in the past (two months ago) and works without
modification on a different PC of a colleague, so chances are
my configuration misses a simple thing, a software package (update) or
