Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 3 of 3 total |
Windows 7 |
Thu, Dec 24 2009 9:47 AM | Permanent Link |
"Sean McDermott" | DBISAM latest - Delphi 2009 Pro
I have a small application that has run well on networks in a peer to peer situation for many years now. I just installed it on a new Windows 7 system as file host (front office) and connected a back office system (XP Pro) as a slave. The front system works fine locally. The path from the back office system is correct. Starting the software on the back system, you can see it loading tables at startup and freezes at about the 10th of 30 tables with a 'not found' error. Using Windows Explorer from the back office XP system, I can browse to the front office Windows 7 system and see the data files so I know the path is correct. But I can't see the file in question so I understand why it freezes. When I go to the front office system the files are all there. If I try and copy the 'missing/hidden' file I get an error saying the file already exists. I have enabled full sharing, I have made sure no files are 'hidden' but still no luck. Last clue is that the file it hangs on is the first of two files that is locked with a password. I provide for this when the data files are loaded with the Session.AddPassword line. Like I said, this app has worked well for many years, networked and on all systems. The only thing new is Windows 7. Last but not least is that the tech that works on their systems has washed his hands of the setup blaming my software and I would like to wash my hands of this issue as I don't think it is my issue, but I can't do that, the client is always right. Anyhow, I am sure or at least hope most of you are up to your eyeballs in eggnog right now and I expect to follow there later today. Many thanks and season's greetings to all, cheers, Sean |
Mon, Dec 28 2009 9:31 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Sean,
<< Using Windows Explorer from the back office XP system, I can browse to the front office Windows 7 system and see the data files so I know the path is correct. But I can't see the file in question so I understand why it freezes. When I go to the front office system the files are all there. If I try and copy the 'missing/hidden' file I get an error saying the file already exists. I have enabled full sharing, I have made sure no files are 'hidden' but still no luck. >> Is the application actually freezing, or are you simply seeing a DBISAM error message ? If the file cannot be seen from the Windows XP system, then the issue is resource sharing/security as it relates to mixing Windows XP and Windows 7. Either way, it is neither your application's fault nor its responsibility if you're using a file-sharing setup - it's the network tech's responsibility. You can easily prove to him that this is the case by popping a DBISAM Database Server on the Windows 7 machine, and opening the table just fine from the Windows XP machine by using DBSYS with a remote connection. << Last clue is that the file it hangs on is the first of two files that is locked with a password. I provide for this when the data files are loaded with the Session.AddPassword line. >> I doubt very much if this has anything to do at all with the problem. -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Dec 28 2009 11:13 AM | Permanent Link |
Sean | Hi Tim, many thanks as always... and Happy New Year, Sean
"Tim Young [Elevate Software]" wrote: Sean, << Using Windows Explorer from the back office XP system, I can browse to the front office Windows 7 system and see the data files so I know the path is correct. But I can't see the file in question so I understand why it freezes. When I go to the front office system the files are all there. If I try and copy the 'missing/hidden' file I get an error saying the file already exists. I have enabled full sharing, I have made sure no files are 'hidden' but still no luck. >> Is the application actually freezing, or are you simply seeing a DBISAM error message ? If the file cannot be seen from the Windows XP system, then the issue is resource sharing/security as it relates to mixing Windows XP and Windows 7. Either way, it is neither your application's fault nor its responsibility if you're using a file-sharing setup - it's the network tech's responsibility. You can easily prove to him that this is the case by popping a DBISAM Database Server on the Windows 7 machine, and opening the table just fine from the Windows XP machine by using DBSYS with a remote connection. << Last clue is that the file it hangs on is the first of two files that is locked with a password. I provide for this when the data files are loaded with the Session.AddPassword line. >> I doubt very much if this has anything to do at all with the problem. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Thursday, March 28, 2024 at 06:05 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |