Replies

Outstanding Mark! Thanks a bunch…it worked perfectly!! Have a great weekend.

Excellent! It sounds like the problem is solved.

Hi Charlotte,
I think I finally uncovered a solution:
Trim(Right([memotest],28-InStr(1,Right([memotest],30),”.”)))
30 is the length of string I want to extract. I used 28 to account for the space between the “.” and the character occupied by the ‘Ctrl-Enter’ (Is there a way to represent this character in an expression?).
As always, thanks for the help.

Initially, this field was to serve as nothing more than a spot to capture random thoughts (as defined by the end-users). It was never intended to be used in reports and people wanted it as simple as possible to jot notes. Now, the need has changed and I have to find a way to make it work on a report.

Do you know of any code that might help me?

That’s a good question and I don’t know the answer. However, why don’t you just save the query and then use VB to run the query? I’m assuming you are creating the SQL in an Access database.

There wasn’t much on the Microsoft site regarding that error and I have never experienced it. I would take the version you converted successfully on your home computer, bring it to work and install it on one of your A2K user’s machines, relink the tables from the v97 back-end and see if that works. If it does, great. If not, then I think your problem rests with the link between the front-end/back-end and not with your version 2000 conversion.
That is at least a first step.

Larry,
Charlotte cleared up bad advice on my part. It does compact correctly on close.

John’s recommendation about compact on close works great. Just be careful if you have multiple users – if two people are in the database and one closes it, the db will begin to compact and will error because you can’t compact a database opened by another user. Also, if you have a front-end and back-end setup, compacting the front-end won’t give you as big a benefit as compacting the back-end.
Just a few things to keep in mind.

Charlotte,
Thanks so much. I can’t believe the subdatasheets had that much of an impact. I removed the subdatasheets and loaded a few tables used for drop-downs on the front-end since they are static. Everything is running fine now.
Thanks and have a great day!

A local front-end/back-end setup works fine. A LAN b/e – local f/e is still painfully slow.
Autocorrect is off and the subdatasheet is on. I’ll turn the subdatsheet off tomorrow and will test performance. I also picked-up additional advice from posts you, Mark and Wendell made earlier this year to a similar question.
Thanks!

Hi Mark,
I was doing some research on a question I posed tonight on split database performance. As a result, I came across your post. On the front-end, why is it important to set the default to ‘Exclusive’ mode? This was a new piece of advice to me and one I’ll gladly follow but I just want to understand the impact it has.
Thanks!
Andrew

Hi Mark,
I just want you to know how much time you saved me. I searched for the proper code to select all controls in a form and I ran across your reply to someone else in early September. The code saved me hours and I figured you’d want to know that it came in handy for someone else.
Thanks!!

Thanks a bunch!! I’ve never seen criteria used that way before. It worked great and I appreciate your help!
Cheers,
Andrew

Give this bit of code a try:

DoCmd.Close acForm, “PSTP1”

and repeat it for the other form names.
Hope that helps.

Mark,
Thanks for the help. I used SetFocus to go to the proper control and then ended up using FindRecord to properly find what I needed. For some reason the other code was inconsistent (even with the change you suggested).
Thanks for the idea and have a great week!