bb.donnay-software.com

I encountered this problem with cdx indexes and ADS, I solved it by creating indexes with a different name than the data file (example: parts.dbf -> parts0.cdx ...) and eliminating parts.cdx

messaoudlazhar wrote:I encountered this problem with cdx indexes and ADS, I solved it by creating indexes with a different name than the data file (example: parts.dbf -> parts0.cdx ...) and eliminating parts.cdx

Interesting. I shall have to think about that...

messaoudlazhar wrote:I encountered this problem with cdx indexes and ADS, I solved it by creating indexes with a different name than the data file (example: parts.dbf -> parts0.cdx ...) and eliminating parts.cdx

Actually, I'd like to clarify that our problems are not occurring when using ADS but instead when using the standard DBF + CDX dbe.

Are you saying that your problem, and the fix you made, was done specifically for errors you had when using ADS with CDX indexes?

Regan, did you check the GPO-settings?

Tom wrote:Regan, did you check the GPO-settings?

Hi Tom

I mentioned this to our tech guy and he said the majority of our users do not use proper server / enterprise windows installations and he doesn't think group policy stuff would be related at all.

I'm happy to go back and challenge that if you think he might be mistaken...

Tom,

I am having same issues Reagan is describing but that link you posted is not working.
Do you know what I can search for under Windows doc?

bamunz@earthlink.net wrote:Tom,

I am having same issues Reagan is describing but that link you posted is not working.
Do you know what I can search for under Windows doc?

The link is missing a ) at the end. If you add that it works fine.

Regan,

Were you able try this I did it work for you?

bamunz@earthlink.net wrote:Regan,

Were you able try this I did it work for you?

Uh, no. I passed this on up the chain in my workplace and haven't heard anything since. Their initial reaction was 'that's not applicable to how our customers run our application...'

How widespread is this with your customers?

We get at least 15-25 error reports every day that mention these types of error. This may not seem like a lot, but if every time it happens some part of a sales / web transaction is interrupted and the data written is incomplete, it causes all sorts of problems. And sometimes the problems caused do not show up until much later and the time invested in investigating what went wrong, where it went wrong and what is needed to fix it can be horrendous.

I'm just hoping for an easy fix, something I missed, I guess, because not every Xbase++ developer out there is having the same issues.

It is the same for me alot of transaction issues. It is definitely some Network issue but I don't see a windows update that has caused it.