Thread: MS Access memo datatypes
Does anyone have a work around from MS Access memo data type in Postgres. I don't want to use LOB's either. D. Johnson
I used the text datatype. -----Original Message----- From: D Johnson [SMTP:dspectra@home.com] Sent: Wednesday, January 10, 2001 5:12 AM To: pgsql-interfaces@postgresql.org Subject: MS Access memo datatypes Does anyone have a work around from MS Access memo data type in Postgres. I don't want to use LOB's either. D. Johnson
Yes, Postgres ODBC creates text field data types when I export the MS Access tables. But, the Postgres data types map back to var chars with a limit of 255 chars. I just figured out a way to support memo types and have MSAccess recognize the type when I link tables from Postgres to Access. It won't support the full 32K memo field of Access but it does create 8K memo fields similar to Postgres text data type. Sure is better than 255 characters, and it's simple to set up. Try this: CREATE FUNCTION textfunc (text) RETURNS text as 'SELECT $1;' LANGUAGE 'SQL'; CREATE TYPE memo ( internallength = 8000, externallength=8000, input = textfunc, output= textfunc, send = textfunc, receive = textfunc, default= '-'); ex. CREATE TABLE memotest ( memo id int4, memfld memo ); After you create the function,data type and a table def. then in Access relink your table to the Postgres table definition. In the Access table design tool you can open the table and should see the memo definition with a size of 8K. Dave Johnson Michael Davis wrote: > I used the text datatype. > > -----Original Message----- > From: D Johnson [SMTP:dspectra@home.com] > Sent: Wednesday, January 10, 2001 5:12 AM > To: pgsql-interfaces@postgresql.org > Subject: MS Access memo datatypes > > Does anyone have a work around from MS Access memo data type in > Postgres. I don't want to use LOB's either. > > D. Johnson
D Johnson wrote: > Yes, Postgres ODBC creates text field data types when I export the MS > Access tables. But, the Postgres data types map back to var chars with a > limit of 255 chars. > just wondering if someone can tell me of the progress of frontend for postgresql.. I liked pgaccess it seemed the most complete of what i saw coming from the gui of say msaccess which i use for my invoicing .. i'm trying to decide to most complete platform ( staroffice's adabas DB or postgresql ) to insert my energies into what will be the least arduous transition ..... thanks lee -====
In article <3A627EAA.3094D925@imyourhandiman.com>, lee johnson <lee@imyourhandiman.com> writes >i'm trying to decide to most complete platform ( staroffice's adabas DB or >postgresql ) to insert my energies into what will be the least arduous >transition ..... FWIW, I started out on Adabas D, purely because the ODBC driver worked on Win16 and it was recommend to me. It seemed like a really 'solid' system, but the documentation was appalling. Although, at the time, the only RDBMS I had used was MsAccess. ;o) However, I couldn't the GUI tools to properly work with distributions based on newer versions of glibc (it's version of curses did not like Unix98 PTYs, so I could not admin it via SSH), and the 'complete backup system' it provided was keen to monopolise the tape drive. It was somewhat unpredictable at times and I did get it to dump core a few times. But the main reason I ditched it in favour of PostgreSQL is that I can write my own functions in C and link them into the backend, and I know I can always install the latest bug-fixes without paying more money. And it just keeps getting better with each release... -- Jamie Walker "My dear boy, forget about the motivation. jamie@sagaxis.co.uk Just say the lines and don't trip over the http://www.sagaxis.co.uk/ furniture." (Noel Coward)