Unix Technical Forum

SEO

vBulletin Search Engine Optimization


Go Back   Unix Technical Forum > Database Server Software > PostgreSQL > pgsql Interfaces odbc

Register FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 04-17-2008, 04:27 PM
Fred Parkinson
 
Posts: n/a
Default Working on problem, thanks for driver help

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 descriptionof 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 itat first because all the rest of the boxes continue to display the data ofthe 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 postmaster

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 04-17-2008, 04:27 PM
Andrei Kovalevski
 
Posts: n/a
Default Re: 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

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 04-17-2008, 04:27 PM
Obe, Regina
 
Posts: n/a
Default Re: Working on problem, thanks for driver help

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
[mailtogsql-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.


---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old 04-17-2008, 04:27 PM
Fred Parkinson
 
Posts: n/a
Default Re: Working on problem, thanks for driver help

Thanks for your reply.

There is no real code involved in the issue. My main form, fMain, has a subform, fStudent. When the user picks a student from a drop-down list on fMain, fMain sends the subform fStudent the id of the selected student. Uponreceiving the student id, the subform makes that student record the recorddisplayed for editing by using the code 'Me.RecordsetClone.FindFirst "student_id = " & cstr(id)' followed by (if no error) 'Me.Bookmark = Me.RecordsetClone.Bookmark'

This part works as desired. I have stepped through the problem and found that this code is not run when the problem occurs, thus is not causing the subform to move unexpectedly to the undesired record.

If the user then chooses to edit the (tabbed control displayed) student data by using the Windows operating system functions ctrl-c, ctrl-v or ctrl-x, the form unexpectedly jumps to a new record before the ctrl-? function acts, and the action is then applied to the new, unexpected record!

As for when it started happening, that is unclear, but probably not too long ago. At first the users thought they were making a mistake, that they were in error somehow, and didn't bring it to my attention until yesterday.

Clearly I need to find out if something was changed in the recent past: upgrade to server, or to workstations (tech support has the habit of making changes without telling anyone). One of the techs thinks that a Win XP Office 2002 - Office 2007 compatibility upgrade was done recently on the workstations, so I will pursue that as well as whatever else I or others can thinkof.

Thank you for considering my problem.

Fred


>>> Andrei Kovalevski <andyk@commandprompt.com> 02/21/2008 1:07 AM >>>

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 boxesshow 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 movedto!
>
> 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 updatesto 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 6: explain analyze is your friend

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 06:40 AM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.1.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145