• WSDylan Morley

    WSDylan Morley

    @wsdylan-morley

    Viewing 15 replies - 16 through 30 (of 94 total)
    Author
    Replies
    • in reply to: Access in Thin Client Environment (Access 2000 / Citrix XP MF) #715415

      Wendell,

      Thanks for the reply….

      Yes, our databases are split into FE/BE, we’re experiencing corruption in the back-end of the databases. We also have a single workgroup that we are using for all of our databases & the workgroup seems to be corrupting every now and then as well! Whenever a user then tries to access a table, they receive a ‘Disk or Network Error’. We get round the problem by kicking the users out of the problem database, then simply opening any database via the workgroup? It’s bizarre…

      We’re getting the same thing with VB applications using Access as a back-end, the BE corrupts perhaps 3 or 4 times a week. The advice from Citrix seems to be use latest SP’s, lastest MDAC etc etc, but the servers are all bang up to date.

      We have load balancing in place on the Farm, so users are connected to the least busy server when their desktop loads. This results in multiple servers accessing a single database BE & I’ve read on the Citrix.com forums that a single server should access a multi-user BE to avoid corruption? Is this a valid point…?

      I’m sick of Citrix…..it’s a good idea in theory but causing so many problems…!

      Thanks

    • in reply to: Access in Thin Client Environment (Access 2000 / Citrix XP MF) #714834

      Thanks Charlotte, but how would this stop Access database corruption?? Does this driver cause problems under thin-client?

    • in reply to: Access in Thin Client Environment (Access 2000 / Citrix XP MF) #714835

      Thanks Charlotte, but how would this stop Access database corruption?? Does this driver cause problems under thin-client?

    • in reply to: Form Behaviour (Access 2000) #710020

      Thanks Dave…!

    • in reply to: Form Behaviour (Access 2000) #710021

      Thanks Dave…!

    • in reply to: Force Disconnect (Access 2000) #707473

      Thanks Charlotte, I think I’m going to try and write some sort of COM DLL to do this….if I have any joy I’ll make the source available…!

      It’s even more of a nightmare in our company at the moment – we’ve just moved onto a thin-client network and hardware ID’s logged in the locking files now just display the ID of the server. We’re forcing everyone in through a workgroup to log their user ID as well, but in some cases users are linking tables to BE databases from unsecured DB’s! This means we can’t identify which users are locking files & have no way to remotely disconnect them… brickwall

    • in reply to: Force Disconnect (Access 2000) #707474

      Thanks Charlotte, I think I’m going to try and write some sort of COM DLL to do this….if I have any joy I’ll make the source available…!

      It’s even more of a nightmare in our company at the moment – we’ve just moved onto a thin-client network and hardware ID’s logged in the locking files now just display the ID of the server. We’re forcing everyone in through a workgroup to log their user ID as well, but in some cases users are linking tables to BE databases from unsecured DB’s! This means we can’t identify which users are locking files & have no way to remotely disconnect them… brickwall

    • in reply to: Force Disconnect (Access 2000) #706720

      Thanks Hans, that’s a better version of what I was going to write…!!

      You would’ve thought an admin tool for doing this would’ve been shipped with Access…?!

    • in reply to: Force Disconnect (Access 2000) #706721

      Thanks Hans, that’s a better version of what I was going to write…!!

      You would’ve thought an admin tool for doing this would’ve been shipped with Access…?!

    • in reply to: Duplicate Primary Key (Access 97) #702499

      Yes, the database is compacted when the VB application is first opened & no other users are connected.

      We do have version / OS issues in the company. Some of our users are on thin-client Citrix (office 2000), while others are using NT4 with Access 97. Still, the VB app is compiled with Jet 4 and just creates a DAO.Database object to communicate with the database, version incompatibilites shouldn’t really come into it…

      Maybe I’ll recreate the index, do & repair & compact…….then just hope it doesn’t happen again…!!

      Thanks for responses…

    • in reply to: Duplicate Primary Key (Access 97) #702475

      The field is unique. That’s the dilemma

    • in reply to: Database Conversion (Access 97 > Access 2000) #691171

      Have tried with a few databases and seems very good…

      My only moan is that it only returns TRUE or FALSE, in the case of FALSE I would want to know why it failed (security etc). But it’s going to save time whatever so it’s all good…!

      Thanks

    • in reply to: Database Conversion (Access 97 > Access 2000) #691140

      Was toying with my own conversion program but this looks like exactly what I need. I’ll test this today & let you know how I get on, many thanks for finding….

    • in reply to: Syntax of Update Statement (VB6) #690422

      As far as I can see, there are 3 objects expected in this statement (cnAdmin, SysDefaults & tblPath). Are all 3 supposed to be objects (tblPath.StoredPath ??) and are they all valid within the scope of the statement?

    • in reply to: Tabbed Folder Resize Problem (VB6) #690417

      Even though this might not be your problem, I’ll add this while we’re talking about resolutions…!

      I’ve started using an Autosize class to resize all the window controls as the form is resized. I’ve attached the code as a text file, just save with the .cls extension.

      To use, just declare it at module level as…

      Privare m_Autosize as AutoSize

      …and in the form resize event just put…

      m_Autosize..ResizeForm Me

      …seems to work quite well, controls are resized and placed in the correct positions on the form. Give it a go, should sort your problem out if it is resolution related…

    Viewing 15 replies - 16 through 30 (of 94 total)