hunting for document

[neous]

hello

i just inherited a database at work, one which noone likes of course. i was unable to access the table so i exported them into a new database. i'm by no means a database guy i'm just learning how to use because i need to implement a database into the vb program i'm writing.

i'm trying to edit a letter thats generated when certain criteria are met. but i don't where to look for the document.

could someone please point me to a direction

i appreciate it.

 

[JoeCruse]

What causes the letter to be generated? If it's a button that the user clicks, look at the underlying code of the button to see if the file location is referenced there. Possibly the file location is stored in one of the tables as well?

 

[neous]

thanks

i just found out that i didn't import all the data from the original database, i'm guessing it's because the startup window "front end" is setup in tabs, just a guess.
could you tell me how to get everything form one database to another

i can't see the code that underlies the command button because that particular form was not imported

thank you

 

[JoeCruse]

In your new database, or another blank database, right click out in the middle of the database screen, and choose the "Import" selection. A browse window comes up for you to select a database that you want to import objects(like the form with the code you need to see) from. Follow the steps that come up in the import form, where it allows you to import whatever tables, queries, forms, reports, and modules (code) that you need from the other database. That's it.

 

[neous]

thanks
that's how i imported those files but the original mdb is 33128 Kb and my new mdb is 13832 kb

 

[JoeCruse]

That's a bit large. I'm betting your tables, queries, forms, reports, and code are all in one MDB file. A good practice, in case you are new to Access, is to keep the actual data tables in a separate MDB, called the "Back end", and the forms, queries, reports, and code in another MDB, usually called the "Front end". Splitting it up makes it better for sharing the data and can keep file size down on the MDB your forms and reports are in. I only have one or 2 applications with the data tables kept together with the other objects, and I only do it because they are low volume use apps and single user.

Do a search here on "Front end" or "Back end", and normalization. There is a TON of good stuff here.