Search results

  1. A

    Front end corrupting back end..?

    That's definitely good to know. Unfortunately, it's going to be a tough sell to convince my boss that all of our Access woes are due to Windows 2000; especially after it's been fine for a year and a half. I've been pushing for xp forever now, but no luck. I'd hate to say it on an access...
  2. A

    Front end corrupting back end..?

    The OS reinstall does fix it. Our quick little band-aid is to just switch the machine with somebody else's. But I'm hesitant to think it’s something on the profile level because I logged in as a different windows user (which I would assume would use a different profile) but the same db user...
  3. A

    Front end corrupting back end..?

    Oh it's my pleasure. I can't tell you how many times I've searched to find that someone else posted a solution and solved my issue. I figure it's the least I could do to give back to the AWF community. Unfortunately however, I'm still in the dark as to why it is happening. I have found a few...
  4. A

    Front end corrupting back end..?

    I think I just got to the bottom of it. The reinstall did no good either. What I had to do is give the user a new username/password and voila problem solved. Pretty bizarre issue if you ask me. I'm gonna take a look at the security file and possibly rebuild it. I can't thank you guys enough...
  5. A

    Front end corrupting back end..?

    You guys have definitely got me a lot closer to finding the culprit than I was yesterday. I've been monitoring the ldb file, and I found that one user that has been in the DB every time it's crashed. So I looked at his ldb from his mde file and low and behold it is showing corruption. It...
  6. A

    Front end corrupting back end..?

    Thank you for our time and I certainly appreciate your input. At least I have some avenue to possibly diagnose the problem. After I posted it, I realized that ADO actually has a property to set the record locking, so I'm going to try to look at that. Thanks again!
  7. A

    Front end corrupting back end..?

    Hmmm, none of my forms make use of recordlocking, however, I also don't have anything bound to the forms. Everything is run in VBA with ADO. Would the recordlocking still apply to the ADO queries?
  8. A

    Front end corrupting back end..?

    Regarding #2, how did you enable record locking? Was it through ado?
  9. A

    Front end corrupting back end..?

    Hey guys- Having quite the issue with corruption lately and I don't quite know how to even begin to troubleshoot this problem, yet I've found a way to fix it, so I guess that's a start. Here's the dilemma: We're running Access 2003 with Windows 2000 on all of the machines. When my users log...
  10. A

    Problem editing values returned by query

    Hi Guys- I have three tables in this scenario: tblFunction, tblContractorFunction, and tblInvoiceFunction. tblContractorFunction and tblInvoiceFunction have a 1-M relationship to tblFunction yet share FunctionType as the common foreign key (which is actually a text value). I want the query to...
  11. A

    How do I identify a variable column from ADO query?

    Thanks banana, That worked perfect! I'd really like to, but I've 3 different recordsets using a criteria from an identifier in a multi listbox just to complete one row in excel. It's actually a really haphazard way of making this report, and I'm well aware of it, but here's my problem. For a...
  12. A

    How do I identify a variable column from ADO query?

    Hi all- I have an excel spreadsheet that has column headers that are identical to the column headers that are in an ADO crosstab query I'm running. What I would like to do is take the name of the excel header and use it to call the column identifier in ADO for a report I'm making. I'm just...
  13. A

    Help with data loss resulting from referential integrity

    Thanks Neil- Turns out this wasn't as bad of a deal as I thought. Along with the INSERT INTO SQL that I ran, I also wrote a VBA routine that verified everything for me. As it turns out my SQL idea didn't work so well as there were some things that were missing. All is fine and dandy...
  14. A

    Help with data loss resulting from referential integrity

    Gotcha! And it seems to be working like a charm. I'm still going through it now, but I'm even making use of the subqueries you taught me earlier rather than typing out thousands of ID's: INSERT INTO tblInvoiceFunction (InvoiceFunctionID, FunctionID, FunctionType, Price, InvoiceColumn) SELECT...
  15. A

    Help with data loss resulting from referential integrity

    Yes and no... I see the difference and what each does, but I'm still not sure if I need to turn auto number off..?
  16. A

    Help with data loss resulting from referential integrity

    I'm still a little confused... So when it inserts the backup into the source table, isn't it going to want to renumber it? Or does the Insert Into query override that?
  17. A

    Help with data loss resulting from referential integrity

    Even though not everything is fk with Client ID? For example: tblClient (PK ClientID) tblJob (PK JobID) [FK ClientID] tblFunction (PK FunctionID) [FK Job ID] In my database, all of the tblFunction records are missing even though they don't have ClientID as it's FK. In your solution, do I...
  18. A

    Help with data loss resulting from referential integrity

    What is '<the new seed>'? Not quite sure I follow your second idea though...
  19. A

    Help with data loss resulting from referential integrity

    I figured I had my work cut out for me... George, how does one reseed a table? I was going to go with your second route, but the first way looks way more appealing.
  20. A

    Help with data loss resulting from referential integrity

    Hi guys- I lost an incredibly large amount of information from my database....and I need some help. Let me give some background: Let me begin by saying this is affecting most of the tables in my back end. Long story short- a record from tblClient was erased, and everything downstream from...
Back
Top Bottom