Support Forums - View Thread

View Thread

The following is the text of the current message along with any replies.

Messages 1 to 3 of 3 total

Wed, Feb 26 2014 4:07 PM	Permanent Link
Michael Fullerton	I have an older app running EDB 2.10. A customer is reporting a 1004 when a record is added to a certain table using AppendRecord and then flushbuffers. This table contain two fields, an integer and a date. The primary index includes both fields. Each field also has its own index as well. The primary index seems to be the first index. The odd thing though is that I have the customer's data and I don't see the problem here locally or when accessing on a shared network folder. What could the difference be? It sounds a bit like the cachedupdates problem fixed in 2.15 but I'm sure the primary is the first index.
Fri, Feb 28 2014 5:33 PM	Permanent Link
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com	Michael, << I have an older app running EDB 2.10. A customer is reporting a 1004 when a record is added to a certain table using AppendRecord and then flushbuffers. This table contain two fields, an integer and a date. The primary index includes both fields. Each field also has its own index as well. The primary index seems to be the first index. The odd thing though is that I have the customer's data and I don't see the problem here locally or when accessing on a shared network folder. What could the difference be? It sounds a bit like the cachedupdates problem fixed in 2.15 but I'm sure the primary is the first index. >> Are you using cached updates ? Tim Young Elevate Software www.elevatesoft.com
Sat, Mar 1 2014 12:03 AM	Permanent Link
Michael Fullerton	"Tim Young [Elevate Software]" wrote: Michael, << I have an older app running EDB 2.10. A customer is reporting a 1004 when a record is added to a certain table using AppendRecord and then flushbuffers. This table contain two fields, an integer and a date. The primary index includes both fields. Each field also has its own index as well. The primary index seems to be the first index. The odd thing though is that I have the customer's data and I don't see the problem here locally or when accessing on a shared network folder. What could the difference be? It sounds a bit like the cachedupdates problem fixed in 2.15 but I'm sure the primary is the first index. >> Are you using cached updates ? Tim Young Elevate Software www.elevatesoft.com No I'm not using cached updates.