Search results

  1. O

    Deal with tables that are "too large" to edit

    Funny you say that. I'm a co-op student here, so my "retirement" from this job is three weeks away. The guy replacing me has much less access experience too. That coupled with the fact that I have lots of other stuff on my plate = no radical changes.
  2. O

    Deal with tables that are "too large" to edit

    Thanks for all the replies. I fixed this particular problem. If I came as annoyed/argumentative, I apologize. This database is just frustrating to deal with and I'm forced to apply "bandage" solutions.
  3. O

    Deal with tables that are "too large" to edit

    Oddly enough, if you try to enter in a idnumber like 5000.A000 via the forms (i.e. you're on the main page for this subject and go to add a record in this IQ table) it lets you. And that's what I did. I know this database design and implementation is not optimal. But, as I said, I don't have...
  4. O

    Deal with tables that are "too large" to edit

    Umm, the table works fine for entering/changing data or reading data via forms. I can also use it via SAS easily (and do so often). The only thing I cannot do is change the structure. I know its a problem, but not as big a problem as you seem to make it. In fact, one of the reasons I would be...
  5. O

    Deal with tables that are "too large" to edit

    As I said, I don't have the time (or expertise) to implement this as it seems like a lot of work, re-making forms etc.
  6. O

    Deal with tables that are "too large" to edit

    Actually, each field is a score on part of an IQ test and the resulting % or Z-score. So, each entry has a different range of possible values, and even number types. And predicting a question, no the % and Z-scores are not calculate automatically but by someone scoring the test by hand and...
  7. O

    Deal with tables that are "too large" to edit

    Yeah, I've read that article and tried the work-arounds and it didn't help. If I were to split the table, how much work would I have to do in order to make the forms work as usual? The table is also pretty normalized. Each attribute depends only on the primary key and the table is in 2NF...
  8. O

    Deal with tables that are "too large" to edit

    Well, at the moment I don't have the time to re-design the table. I know it needs to be done, though. And I'm not sure what you mean by "smart key". There is an input mask and I just need to change it to accommodate new idnumbers. I could remove the input mask if that's better.
  9. O

    Deal with tables that are "too large" to edit

    There are 200 fields in the table. The primary key, (the Idnumber) has an input mask of 0000&0000 and I want to change it to 0000&AAAA
  10. O

    Deal with tables that are "too large" to edit

    I inherited a db and one of the tables is giving me problems when trying to change some of the design. Namely, I make the change and when I try to save it says "Property value too large.". I did a compact/repair. Beyond that, I can't remove any of the columns and am not sure what to do. Thanks.
  11. O

    Form not auto-filling with data.

    I have a database (inherited) and its now working well except for one form. You can open it and enter data and save/close it. But when you open it again, there is nothing there (whereas all the other forms show the current data). The code is included below. I've done some debugging and found...
  12. O

    "Transferring" tables structure.

    Just a thought before I try your suggestion. What if I simply copy the current table and past it into the old table, using the "append" option? In this case, it would also require matching file size. It seems to also ignore validation. The only other problem is new variables but there are very...
  13. O

    "Transferring" tables structure.

    I'll try that. the field names and types are the only things preserved in the new tables, so that's good.
  14. O

    "Transferring" tables structure.

    Hello all. I have a database that has up-to-date data but is missing all the structure (I won't go into why this happened...). I have a backup version that has the exact same tables but with all the structure (i.e. primary keys, validation, default values etc.) intact. Is there a way to get...
  15. O

    Splitting database causes VBA error in form

    Okay, how about this then. Is there a way for me to temporarily "turn off" any restrictions when pasting a batch of data from one table to another?
  16. O

    Splitting database causes VBA error in form

    Thanks, I'll check it out. Just for reference, Table 1 is the one with the good data and Table 2 is the one with the good structure. I tried to do this manually, but since the Table 2 has some restrictions, some of Table 1 can't be pasted into Table 2. Is there a way to code this so it ignores...
  17. O

    Splitting database causes VBA error in form

    The reason I think it is 2003 is because whether it is the current version or backup versions from April, they work fine in 2000 but not in 2003 (work fine referring to being able to edit code). So if something has gone with wrong with compiled code, it doesn't seem like this should be the case.
  18. O

    Splitting database causes VBA error in form

    Awesome; worked like a charm. Some other questions... not necessarily VBA so let me know if I should make a new topic elsewhere. 1) Access 2003 gives me warnings about "unsafe expressions not blocked" everytime I open the db. Any way around this (so they stop showing up)? 2) Is there any way...
  19. O

    Splitting database causes VBA error in form

    Thanks, I'll try that. And yeah, I did Compact/Repair. I think it has something to do with 2003 vs 2000, as using it with a machine running 2000 is fine.
  20. O

    Splitting database causes VBA error in form

    First, the crashing seems to be caused by me using 2003 while the Access file is 2000. I'm editing it on a computer using 2000 now, and when I test the form, its giving me a syntax error, with a missing operator in 'table_name = Module A'
Back
Top Bottom