Bookmarks

Yahoo Gmail Google Facebook Delicious Twitter Reddit Stumpleupon Myspace Digg

Search queries

WwwxxXdbf, procmail "FROM_MAILER" patch, Use of assignment to $[ is deprecated at /usr/local/sbin/apxs line 86. , wwwxxx vim, mysql closing table and opening table, 800c5000, setgid operation not permitted, pciehp: acpi_pciehprm on IBM, WWWXXX.DBF, 078274121

Links

XODOX
Impressum

#1: problem updating from form

Posted on 2011-01-06 07:12:29 by Karen Springer

This is a multi-part message in MIME format.
--------------060507030806050105060106
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

I have a problem that has me stumped.

We have a table that is the main table (tbl_Assemblies) in a production
Microsoft Access application. Our users are complaining that sometimes
they enter data in the form, move off of the record & then upon
returning to the record the data reverts back to what existed in the
field prior to the entry. These complaints have recently become more
frequent. This is an intermittent problem, but I have been able to
replicate the issue consistently on one particular record. There isn't
anything unusual about the data.

We are using PostgreSQL 8.1.4 on RHEL 4.1, Microsoft Access 2002 &
psqlodbc 8.01.0200 though I have tried psqlodbc 9 with this
configuration. I am aware that our postgres major & minor versions are
out of date. We are looking at that now.

When we have a problem record, I can update at the table level from
Access, but not in the form. I have isolated the table, removing any
foreign keys from the table. There aren't any triggers. I created a
new Access DB with only the table & a crude form with only the primary
key & the work order field. I have played around with the ODBC
settings. We have vacuumed, reindexed & performed a full vacuum on the
Postgres DB multiple times. None of these actions have had a positive
effect. I have looked at pg_stat_activity & pg_locks for open
transactions & row locks. I created an identical copy of the table &
imported all of the data, about 194,000 records, into it. I saw the
same problem results until I removed all, but about 20 records. Only
then was I able to get the update from a form to stick on our test
record. Incidentally, the production Access DB grows in size rapidly,
from 14MB after a repair & compact to 400 MBs a day or two later.

Here is the table structure with the foreign keys removed.
CREATE TABLE "Production_Tracking"."tbl_Assemblies"
(
"BarCode" varchar(12) NOT NULL,
"PartNumber" varchar(32) NOT NULL,
"LRU" varchar(20),
"PartsListRev" varchar(10),
"SerialNumber" float8,
"MTN" varchar(15),
"DocNum" varchar(50),
"Comments" text,
"SupplierNo" varchar(7),
"DrawingNoRev" varchar(10),
"WorkOrder" varchar(8),
"BldStdRev" varchar(15),
"Quantity" int4 NOT NULL DEFAULT 1,
"Salesorder" varchar(8),
"WOQuantity" int4,
CONSTRAINT "pkey_BarCode" PRIMARY KEY ("BarCode")
)
WITHOUT OIDS;

I can provide the ODBC logs if helpful. I've noticed that the logs do
not show the xmin field.

Here are the ODBC settings:
Unicode
Disable Genetic Optimizer = True
KSQO(Keyset Query Optimization) = True
Recognize Unique Indexes = True
Use Declare/Fetch = False
ComLog (C:\psqlodbc_xxx.log) = False
Parse Statements = False
Cancel as Free Stmt (Exp) = False
MyLog (C:\mylog_xxxx.log) = False
Unknown Sizes = Maximum
Text as LongVarChar = False
Unknowns as LongVarChar = False
Bools as Char = True
Max Varchar = 254
Max LongVarChar = 8190
Cache Size = 100
SysTable Prefixes: dd_;
Read Only = False
Show System Tables = False
LF <-> CR/LF conversion = False
Updateable Cursors = False
byea as LO = False
Row Versioning = True
Disallow Premature = False
True is -1 = True
Server side prepare = False
use gssapi for GSS request = False
Int8 As = default
Level of rollback on errors = Transaction

I apologize for the length & detail of this message. I would greatly
appreciate any help.

Thank you,
Karen

**

--------------060507030806050105060106
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
I have a problem that has me stumped. <br>
<br>
We have a table that is the main table (tbl_Assemblies) in a
production Microsoft Access application.&nbsp; Our users are complaining
that sometimes they enter data in the form, move off of the record
&amp; then upon returning to the record the data reverts back to
what existed in the field prior to the entry.&nbsp; These complaints have
recently become more frequent.&nbsp; This is an intermittent problem, but
I have been able to replicate the issue consistently on one
particular record.&nbsp; There isn't anything unusual about the data.<br>
<br>
We are using PostgreSQL 8.1.4 on RHEL 4.1, Microsoft Access 2002
&amp; psqlodbc 8.01.0200 though I have tried psqlodbc 9 with this
configuration.&nbsp; I am aware that our postgres major &amp; minor
versions are out of date.&nbsp; We are looking at that now.<br>
<br>
When we have a problem record, I can update at the table level from
Access, but not in the form.&nbsp; I have isolated the table, removing
any foreign keys from the table.&nbsp; There aren't any triggers.&nbsp; I
created a new Access DB with only the table &amp; a crude form with
only the primary key &amp; the work order field.&nbsp; I have played
around with the ODBC settings.&nbsp; We have vacuumed, reindexed &amp;
performed a full vacuum on the Postgres DB multiple times.&nbsp; None of
these actions have had a positive effect.&nbsp; I have looked at
pg_stat_activity &amp; pg_locks for open transactions &amp; row
locks.&nbsp;&nbsp; I created an identical copy of the table &amp; imported all
of the data, about 194,000 records, into it.&nbsp; I saw the same problem
results until I removed all, but about 20 records.&nbsp; Only then was I
able to get the update from a form to stick on our test record.&nbsp;
Incidentally, the production Access DB grows in size rapidly, from
14MB after a repair &amp; compact to 400 MBs a day or two later.<br>
<br>
Here is the table structure with the foreign keys removed. <br>
CREATE TABLE "Production_Tracking"."tbl_Assemblies"<br>
(<br>
&nbsp; "BarCode" varchar(12) NOT NULL,<br>
&nbsp; "PartNumber" varchar(32) NOT NULL,<br>
&nbsp; "LRU" varchar(20),<br>
&nbsp; "PartsListRev" varchar(10),<br>
&nbsp; "SerialNumber" float8,<br>
&nbsp; "MTN" varchar(15),<br>
&nbsp; "DocNum" varchar(50),<br>
&nbsp; "Comments" text,<br>
&nbsp; "SupplierNo" varchar(7),<br>
&nbsp; "DrawingNoRev" varchar(10),<br>
&nbsp; "WorkOrder" varchar(8),<br>
&nbsp; "BldStdRev" varchar(15),<br>
&nbsp; "Quantity" int4 NOT NULL DEFAULT 1,<br>
&nbsp; "Salesorder" varchar(8),<br>
&nbsp; "WOQuantity" int4,<br>
&nbsp; CONSTRAINT "pkey_BarCode" PRIMARY KEY ("BarCode")<br>
) <br>
WITHOUT OIDS;<br>
<br>
I can provide the ODBC logs if helpful.&nbsp; I've noticed that the logs
do not show the xmin field.<br>
<br>
Here are the ODBC settings:<br>
Unicode<br>
Disable Genetic Optimizer = True<br>
KSQO(Keyset Query Optimization) = True<br>
Recognize Unique Indexes = True<br>
Use Declare/Fetch = False<br>
ComLog (C:\psqlodbc_xxx.log) = False<br>
Parse Statements = False<br>
Cancel as Free Stmt (Exp) = False<br>
MyLog (C:\mylog_xxxx.log) = False<br>
Unknown Sizes = Maximum<br>
Text as LongVarChar = False<br>
Unknowns as LongVarChar = False<br>
Bools as Char = True<br>
Max Varchar = 254<br>
Max LongVarChar = 8190<br>
Cache Size = 100<br>
SysTable Prefixes:&nbsp; dd_;<br>
Read Only = False<br>
Show System Tables = False<br>
LF &lt;-&gt; CR/LF conversion = False<br>
Updateable Cursors = False<br>
byea as LO = False<br>
Row Versioning = True<br>
Disallow Premature = False<br>
True is -1 = True<br>
Server side prepare = False<br>
use gssapi for GSS request = False<br>
Int8 As = default<br>
Level of rollback on errors = Transaction<br>
<br>
I apologize for the length &amp; detail of this message.&nbsp; I would
greatly appreciate any help.<br>
<br>
Thank you,<br>
Karen<br>
<div class="moz-signature"><br>
<o:smarttagtype
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"><o:smarttagtype
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="country-region"><o:smarttagtype
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="State"><o:smarttagtype
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City">
<div class="Section1"><span style="font-size: 8pt;
font-family: Tahoma;"><o:p></o:p></span> </div>
</o:smarttagtype></o:smarttagtype></o:smarttagtype></o:smarttagtype><b><span
style="font-size: 10pt; font-family: Tahoma;"><o:p></o:p></span></b></div>
</body>
</html>

--------------060507030806050105060106--

Report this message