I build one conduit with pfgPalmSyncComponent, I look Contacs sample, but when pfgPalmSyncComponent_TomaPedidos.Sync(props) start nothing happends, the cursor in Wait SQL mode. Review code line by line but I'cant work my conduit.
Any idea?
Thank
PTTK
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Unfortunately, the contacts example is the one example I didn't write myself, and it relies on a third party local database library. If you're having trouble getting it to work, check out the readme.txt file that comes with the example for information on where to get the library.
If you still have trouble, I'm not sure what else to suggest. Try extracting the offending code and putting it in a test application - this will at least eliminate any synchronisation issues and allow you to properly test the databasing to get it right before returning to getting the conduit to run properly.
DreamMaster.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If it's freezing when the data module is freed, then it's being caused by one of the components on the data module form being freed. Perhaps one of your query components.
I'd treat this "fix" with caution - you're getting around it by not properly freeing the resources used by the application, and that's always a big no-no with Windows - you end up with memory leaks and so on.
Whilst I can't offer much in the way of advise, since the problem is occurring with the query components rather than the actual core conduit library, my previous advise stands - try copying and pasting the same query access code to a separate test application to see if the problem still occurs, and chase it down from there. You might also want to post for help a forum more devoted to the query components than for the general conduit library, since as I said, I'm unable to help much with third-party components/libraries.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I build one conduit with pfgPalmSyncComponent, I look Contacs sample, but when pfgPalmSyncComponent_TomaPedidos.Sync(props) start nothing happends, the cursor in Wait SQL mode. Review code line by line but I'cant work my conduit.
Any idea?
Thank
PTTK
I install "Conduit Contacts" sample and happens the same, the cursor in wait SQL mode for ever.
Thank
PTTK
The problem is :
ContactsmQuery.Open;
when execute this instruction the conduit stop!!, tha same happens with ADOQuery
Any idea?
Thank
PTTK
The same problem with : ContactsmQuery.ExecSQL, when execute this instruction the conduit stop!!,
Unfortunately, the contacts example is the one example I didn't write myself, and it relies on a third party local database library. If you're having trouble getting it to work, check out the readme.txt file that comes with the example for information on where to get the library.
If you still have trouble, I'm not sure what else to suggest. Try extracting the offending code and putting it in a test application - this will at least eliminate any synchronisation issues and allow you to properly test the databasing to get it right before returning to getting the conduit to run properly.
DreamMaster.
Thank Paul,
The problem is with all Query component (Dbxepress, ADO, mQuery....), when try "Open" or "ExecSQL" the conduit halt!.
I build all new code, but the problem is the same.
Any idea?
Thank again
PTTK
Hi,
I found the problem :
finalization
begin
//DataModule_TomaPedidos.free;
end;
When include instruction DataModule.Free and conduit finish, FREEZE application.
That all!!!
Thank
PTTK
If it's freezing when the data module is freed, then it's being caused by one of the components on the data module form being freed. Perhaps one of your query components.
I'd treat this "fix" with caution - you're getting around it by not properly freeing the resources used by the application, and that's always a big no-no with Windows - you end up with memory leaks and so on.
Whilst I can't offer much in the way of advise, since the problem is occurring with the query components rather than the actual core conduit library, my previous advise stands - try copying and pasting the same query access code to a separate test application to see if the problem still occurs, and chase it down from there. You might also want to post for help a forum more devoted to the query components than for the general conduit library, since as I said, I'm unable to help much with third-party components/libraries.
Any way, thank Paul
PTTK