Re: Working on problem, thanks for driver help
От | Obe, Regina |
---|---|
Тема | Re: Working on problem, thanks for driver help |
Дата | |
Msg-id | 53F9CF533E1AA14EA1F8C5C08ABC08D2033A5115@ZDND.DND.boston.cob обсуждение исходный текст |
Ответ на | Re: Working on problem, thanks for driver help (Andrei Kovalevski <andyk@commandprompt.com>) |
Список | pgsql-odbc |
This is strange indeed. Could be an Access issue though. Which version of MS Access are you using? Also I'm guessing something as bizarre as this could happen if your parent-child relationships between your forms changed and somehow the field you are pasting into or cutting text out of is one of the parent-child fields. What are your parent-child fields set to on your master/sub forms? How this could happen without you actually changing the form is if your postgresql table changed - e.g. you added a field in between another set of fields. Since linked tables do not refresh without explicitly refreshing them, your linked primary key field could very well be now pointing at one of the parent child fields. I would try relinking your postgresql tables to rule that out as an issue. Hope that helps, Regina -----Original Message----- From: pgsql-odbc-owner@postgresql.org [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Andrei Kovalevski Sent: Thursday, February 21, 2008 4:08 AM To: Fred Parkinson Cc: pgsql-odbc@postgresql.org Subject: Re: [ODBC] Working on problem, thanks for driver help Hello, It's hard to understand your problem. When did your problem appear? Show us your ODBC + PostgreSQL relative code. Fred Parkinson wrote: > I tried 8.01.02 to replace my old one, but the problem persists. > > I will keep trying newer versions, but I thought I might post a description of the problem in the meantime in case someone has seen it or has suggestions. > > In my app. I have a subform which has a tab control with student information, and the form source is table tStudents, a postgres table. > > This form is embeded in another form, fMain. > > Odd thing is, if I do a Ctrl-V to paste text into a text box on the tab, the form moves to a new record and pastes the data there instead of to the original record that was displayed! The form has moved to the new record before the 'before update' event of the text box has fired. > > This happens if I paste into a box on either tab page. You don't notice it at first because all the rest of the boxes continue to display the data of the original record, until you click on another tab. Then all the boxes show the new unwanted record, and there the pasted data is. > > Ctrl-X (cut) has the same problem. Things look good at first, then you notice that you removed data from a different record that the form has moved to! > > It doesn't happen when I copy all the postgres data into a local access table and then use it as the record source instead of the postgres table. This is what makes me think it may be an odbc driver issue. > > Ctrl-V and Ctrl-X are windows functions (I'm on Win XP Professional, not sure which SP) so concievably Win is part of the problem. I will set up a box with an earlier version of XP and see what happens. > > This app has been running smoothly for years, and through several updates to the backend postgres database. > > Thanks in advance for any help, if I solve it I will post a solution. > > Fred > > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaste -- Andrei Kovalevski PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/ ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match ----------------------------------------- The substance of this message, including any attachments, may be confidential, legally privileged and/or exempt from disclosure pursuant to Massachusetts law. It is intended solely for the addressee. If you received this in error, please contact the sender and delete the material from any computer.
В списке pgsql-odbc по дате отправления: