 |
BorlandTalk.com
Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
lakis
Guest
|
 Posted: Tue Mar 22, 2005 10:27 am Post subject: datasnap access violation |
 |
|
i have used datasnap remote data module to create a multi tier database
application...
i have placed in the remote data module an ado connection ,4 ado tables and
4 dataset providers..i
have also (of course a form1)..i want to when i click the start/shutdown
button on the Form1 to stop or start the datasnap server...when i try to
stop the adoconnection (with connected->false,or cancel()) i get an access
violation,same for the tables(adotable->active=false) the same for the
dataset providers..it seems that i cant change anything in the remote data
module by using a button on the form1...of course i have included the file
header(
the funny thing is that if i put an adoconnection in my form and use a
button to start stop it ,it works perfectly!
|
|
| Back to top |
|
 |
Mark Guerrieri
Guest
|
| Posted: Thu Mar 31, 2005 10:25 pm Post subject: Re: datasnap access violation |
|
|
| Quote: | i have used datasnap remote data module to create a multi tier database
application...
i have placed in the remote data module an ado connection ,4 ado tables
and
4 dataset providers..i
have also (of course a form1)..i want to when i click the start/shutdown
button on the Form1 to stop or start the datasnap server...when i try to
stop the adoconnection (with connected->false,or cancel()) i get an access
violation,same for the tables(adotable->active=false) the same for the
dataset providers..it seems that i cant change anything in the remote
data
module by using a button on the form1...of course i have included the file
header(
the funny thing is that if i put an adoconnection in my form and use a
button to start stop it ,it works perfectly!
|
By design, the DataSnap server should be running on one machine (with no
user interface) and the client that accesses it should be running on another
machine. At the least, they would be running in seperate prcesses on the
same machine. Either way, there is no way to directly access the
properties/methods of the components on the RDM from the client app. Your
access violations are most likely the result of accessingg NULL/undefined
pointers, since the form in the client has no access to the components in
the RDM.
Mark
|
|
| Back to top |
|
|
billaras1234
Guest
|
| Posted: Fri Apr 01, 2005 10:34 am Post subject: Re: datasnap access violation |
|
|
if i have understood correctly you mean to create a separate function inside
the remore data module to activate ore not the compnents inside it (like ado
tables..) and to call this function from another form..i have done this and
i still get a access violation in memory...i dont understand what is going
on..once the rdm starts nothing cant change it?
i believe that there must be a way or it might be a borland bug
Ο "Mark Guerrieri" <mguerrieri (AT) nospam_cmsgrp (DOT) com> έγραψε στο μήνυμα
news:424c78d6$1 (AT) newsgroups (DOT) borland.com...
| Quote: | i have used datasnap remote data module to create a multi tier database
application...
i have placed in the remote data module an ado connection ,4 ado tables
and
4 dataset providers..i
have also (of course a form1)..i want to when i click the start/shutdown
button on the Form1 to stop or start the datasnap server...when i try to
stop the adoconnection (with connected->false,or cancel()) i get an
access
violation,same for the tables(adotable->active=false) the same for the
dataset providers..it seems that i cant change anything in the remote
data
module by using a button on the form1...of course i have included the
file
header(
the funny thing is that if i put an adoconnection in my form and use a
button to start stop it ,it works perfectly!
By design, the DataSnap server should be running on one machine (with no
user interface) and the client that accesses it should be running on
another
machine. At the least, they would be running in seperate prcesses on the
same machine. Either way, there is no way to directly access the
properties/methods of the components on the RDM from the client app. Your
access violations are most likely the result of accessingg NULL/undefined
pointers, since the form in the client has no access to the components in
the RDM.
Mark
|
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
