Shared databases & PSF

Author:   Cal K  (---.asm.bellsouth.net) Date:   08-07-07 21:27 I am a database software developer. Recently a long standing cliient of mine, who has run his business using a custom database app developed by me, had his hardware service company install PSF on his Win2003 Small Business Server. A short wile after that, it was discovered that the database app no longer honored systematically placed record locks which prevent simultaneous access to records being edited. Extensive testing has verified that indeed the locks are being made and held for the time required, just no honored by other stations on the network. Is there any record of similar problems when using PST? The database app is about 12 years old and the routines which read, lock, edit, write, and unlock record sets haven't been touched in over ten years. I suspect PSF may be the root of this issue. Any experience, anyone? Cal

Reply To This Message

Re: Shared databases & PSF

Author:   Oliver Vukovics  (---.dip.t-dialin.net) Date:   08-22-07 18:16 Dear Cal, >I am a database software developer... Which network protocoll are you using for this database? Public ShareFolder us the Microsoft DCOM protocoll as network transport protocoll. If you also would use this protocoll, I think it could give same conflicts but it is not a must. If you use only TCP/IP it is a complete other protocoll and so we do not think that there is an relation between your database and PSF. We do not get any simular error messages. I think you searched also in the forum and did not find any error messages like yours. An easy way to see if there are any conflicts between both products would be to deactivate Public ShareFolder in the network. Kind regards Oliver SDMD support

Reply To This Message

Advice:

This forum is closed. No further postings can be created here.

Please use our new forum...

If your question is still unanswered, please post it again in the new forum.