On Dec 18, 2018, at 1:05 PM, Anrik Drenth <dren...@gmail.com> wrote: > > Couple of good insights there. Would you have example python code that shows > the Unicode-to-ASCII conversion in action? > > So 0x000000000189CF01 to 003F49 > > The current code is written in Python 2.7, its selecting the data from SQL > Server and writing it into Access 97. > As Access 97 is somewhat dated we want to get rid of this code and hand > responsibility back to the client. > > The sql server timestamp field is a rowid. It was used back in the day under > the mistaken assumption it was a datetime field. It is not, subsequently the > field exists but has never been used.
Aha. Here's my alternate theory, then. I'll bet that field in the Access table is declared as "AutoNumber". In that case, Access would be assigning its own unique row number to the field, totally ignoring the incoming field from SQLServer. That would make a certain amount of sense, but you'd have to look at the other values in that field to be sure. > We still have to re-produce the same exact same value in the field on the off > chance it is used by the clients system. Don't you have the code that originally created those fields? It is absolutely pointless for us to guess how this was done. — Tim Roberts, t...@probo.com Providenza & Boekelheide, Inc.
_______________________________________________ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
