How can i close an non responding ADP file w/o killing the process?
Hi Experts,
I am trying to close an non responding ADP, however I would try to avoid killing the process thru task manager in order to avoid risk of corruption, already tried Cntrl+Break and didn't help, any other safe solution?
I am trying to close an non responding ADP, however I would try to avoid killing the process thru task manager in order to avoid risk of corruption, already tried Cntrl+Break and didn't help, any other safe solution?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
@bfuchs,
If you compiled the changes and saved the changes before starting the process, you are not likely to corrupt the FE.
@Jeff,
I thought ADP's were tied to a specific SQL server version.
If you compiled the changes and saved the changes before starting the process, you are not likely to corrupt the FE.
@Jeff,
I thought ADP's were tied to a specific SQL server version.
ASKER
@Jeff,
My version of office is 2000 and SQL BE is SQL Express 2005, although some users have office 2003 running on their pc.
Do you think killing the BE task of this user from SSMS first would be a better option?
My version of office is 2000 and SQL BE is SQL Express 2005, although some users have office 2003 running on their pc.
Do you think killing the BE task of this user from SSMS first would be a better option?
@Pat
I was not sure either...
;-)
I was just mentioning that since ADP's were deprecated, ...I was not sure if the Access/SQL or OS version could be the culprit...
I was not sure either...
;-)
I was just mentioning that since ADP's were deprecated, ...I was not sure if the Access/SQL or OS version could be the culprit...
@bfuchs,
I don't have anything prior to Access 2003 running on my PC, so I can't be sure what might be best.
Ultimately you will have to do something soon, ...as keeping a "non responding" db open this long may cause more problems than closing it from the task manager...
JeffCoachman
I don't have anything prior to Access 2003 running on my PC, so I can't be sure what might be best.
Ultimately you will have to do something soon, ...as keeping a "non responding" db open this long may cause more problems than closing it from the task manager...
JeffCoachman
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok Experts,
I guess you all right, waiting always for the App to close will waist more of my time than having to re-program once..
Thanks to all participants!
I guess you all right, waiting always for the App to close will waist more of my time than having to re-program once..
Thanks to all participants!
ASKER