Replies

Thanks Tom,
For some reason, this bit of code just didn’t want to work. I ended up using FindRecord instead and that has worked without a snag.
Thanks for the idea and have a great week!

Isn’t it funny how something so simple can work so great. Hans, I was a bit skeptical but it worked perfectly. Thanks a bunch!!…and Peter thanks for the input as well.

Sorry if I’m being a bit vague. I want to publish the Word Documents so nobody can modify them in any way. I think you’re right, Adobe would be the best way.

That is correct. I want to make sure they can’t copy them from the CD and modify them elsewhere. Most of the files are Word so I can pword protect against writing. However, one file is a Microsoft Binder file and protecting that file doesn’t seem as easy. If I could keep the CD from being copied or modified, that would be great but I don’t think that is possible.
Thanks!

I think if you change the spouse’s last name to guardian’s last name, the query will work for you as listed below:
SELECT DISTINCTROW GUARDIANS.GUARDIAN_ID, GUARDIANS.LAST_NAME & “,” & GUARDIANS.FIRST_NAME & ” ” & GUARDIANS.MIDDLE_NAME AS Expr1
FROM GUARDIANS
WHERE (((GUARDIANS.LAST_NAME)=forms![frmStudents]![Last_name]))
ORDER BY GUARDIANS.LAST_NAME, GUARDIANS.FIRST_NAME;
Also, once you select the student’s last name, you may have to requery the guardian’s drop-down box. For instance, when you open the form, the student’s last name is empty therefore, the guardian’s last name will be based on an empty box. If you set the after update event of the student’s last name to:
Me.NameOfTheGuardianLNameBox.Requery
This will cause the guradian last name to requery to the new entry in the student’s last name.

Thanks Mark. That’s what I feared but was still hopeful. Thanks a lot.

Francois,
Outstanding…thanks a bunch!

Sorry about the confusion. I’m just trying to find a way to keep someone from importing the tables in my database into their own database.

Is there a way to keep someone from creating a database and importing tables from an MDE file to the new database? The forms in the MDE are safe since they’re compiled, however, people can still import the tables.

Thank You Charlotte. I just want to make sure I’m not forcing an MDB to do something that would be better served by an ADP…your notes make it clear I am on the right path using an MDB. It seems like ADP’s throw a lot of extra steps itno the formula. I just wish I had a better grasp of when I should upgrade.

There will be maybe 20 simultaneous users. My client will be using the database on another client’s server. He is afraid of storing the front-end and back-end on his client’s server. Hence the reason for SQL…to keep the data remote so his client can’t take the database and squeeze him out. Someone already started work so I’ve been trying to persuade him to move everything to his client’s server. I plan on locking everything down (MDE) to alleviate his concerns. If you have any recommendations on this issue, I would apprecite reading them. Also, is there a way to lock tables down so someone can’t import them into another table? On MDE files I can still go in and import the data.
Once again…Thanks!

That’s a good question. Every once in a while I receive strange errors using ODBC. I’ve never worked in Oracle so I can’t be much help. Sorry.

Charlotte, that worked perfectly. Thanks a bunch and have a great day!

Thanks! There was plenty of information and I find just the right code to use.

Peter,
If in the long run combining the data into a single table will save time, I would go ahead and do it. However, you must consider how similar the table layouts are of T1 and T2. If they are very similar, it seems best to combine them. If ClientID, month and year are the only consistent elements, then maybe it is best to keep them separate.
Dashiell

Steve,
Bravo! That did the trick. I still don’t know why the original SQL failed. I still receive odd errors from time to time but that’s ok…I can work around them. This one had me stumped so thanks a lot!!
Andrew