Search results

  1. S

    "connection cannot be used" error on production but not development

    Can anyone help with this at all? I'm afraid even if I manage a work around for THIS bit, it's going to keep failing. I just don't understand all this connection code he has throughout this database. Can you maybe help me understand this stuff? Public MAINDB As ADODB.Connection Public Sub...
  2. S

    "connection cannot be used" error on production but not development

    I'm wondering why he has it making this connection at all. The table it's getting the generator status from is in the database. What does the connection provide here??
  3. S

    "connection cannot be used" error on production but not development

    1. In this instance, development and production are two different .mdb files. Both files point to the same database on the same SQL 2012 server. (the reasons doing it this way are beyond the scope of this problem) 2. Windows 7 3. I thought that I'd moved a copy of the production .mdb to my...
  4. S

    "connection cannot be used" error on production but not development

    I'm not sure how that could be an issue. The development copy on my machine works. When I use the production copy on my machine, it doesn't. I built the DSN files that both are using on this machine.
  5. S

    "connection cannot be used" error on production but not development

    Short history: old Access database that's been upgraded through to Access 2000 or 2003 (probably 2000), but not beyond. Was rebuilt in Access 2003 format around 2006/2007 (by someone else who no longer works here). Being used now in Access 2007 and 2010. Uses DSN to connect to SQL Server...
  6. S

    Works in 2003, throws error: 2507 in 2007

    Ok, did some checking. Apparently they just started rolling out computers with Office 2010 on them. It's 2010 this isn't working on. *sigh* Now I have THREE versions of Access I'm trying to support. Anyway, thanks. Now we're looking into rewriting this entire process and automating it in...
  7. S

    Works in 2003, throws error: 2507 in 2007

    I have a complicated series of functions whose purpose is to produce a database file that sits in a folder on our network until a completely separate process in another database sucks it in for reporting purposes. These functions work perfectly in Access 2003. We've begun rolling out Access...
Back
Top Bottom