Replies

You can place one on your report ….. but you can not trigger any events with it.
So basically it would be useless.

RDH

You are welcome …..

In my opinion, there are no dumb questions ….. especially if you need help.

Remember that all questions are easy ….. if you know the answer.

But what can be very simple to one person, can be a major obstical to others.

RDH

You do not need to run the code but one time. It creates the property and sets it. It will remain set until code is executed to change it. I, myself choose not to “clutter” a database” with the necessary code to do this. I use a remote (external) database that will set and unset the property with anyout code place in the app effected. Using this approach also keeps you from having to place a “hidden backdoor” to allow you access should you need to change something.

If you would like a copy of the db I built for doing this, email me and I will send you a copy.

This db will set the ShiftKey property for any Access database version …. Access 97 and up.

rdhicks@mindspring.com

HTH
RDH

You are welcome …..

“Sometimes it’s the little things that get you”

RDH

The only sure way to do this is to set up User Level Security. You can then set the “permissions” for the Groups to not allow access to the specific obects you do not want to to have access to.

HTH
RDH

Sounds like your problem may be at table level and not with your code. The field in the table where you are storing this result may need the “Allow Zero Length” property set to “Yes. The default for this property is “No”.

HTH
RDH

To start with …. Forms are not designed to be printed, you should be using Reports instead.

Have you checked the recordsources that the forms are bound to. Do they return valid records? If they are not, that is the problem.

RDH

I assume you are talking about the 1 and the Infinity symbol (looks like the number 8 on it’s side). This shows to indicate a “One to Many” relationship with “Enforced Referential Integrity”.

HTH
RDH

I did not say you “could not” create joins in in FrontEnd … only that the Database Splitter will not leave any there after the split process ….. they will all be moved to the BackEnd. Also you will not be able to enforce Referential Integity on the linked tables from the BackEnd in the Relationship window of the FrontEnd. If any additional Joins are needed ….. I usually set them up directly at Query level.

RDH

I agree with Mark ….. the Relational Joins are maintained in the BackEnd.

If you use the Database Splitter built into Access … all of the joins are moved to be BackEnd and there should be “none” left in the FrontEnd. If you used the “Splitter” to split the database, I haven’t a clue to how any Relational Joins where left in FrontEnd …. they should not have been.

HTH
RDH

Installing Office XP will include an install of IE6.

HTH
RDH

I agree with Charlotte ….. Installing an earlier version of an Office product can be very, very dangerous. To do it properly you must perform the installs in the “version order”. I had a similar problem a while back on a machine at work. I stayed on the phone with Microsoft Tech Support for an hour and a half. They tried every trick they knew to straighten out the problem but never figured it out. I ended up having to reformat the drive and reinstall all software. I have Office 97, 2000 and XP on my machines but this must be done very carefully and also must be done starting with the installation of the earliest version first.

Here is a MS Knowledge base article that may help.

Running Multiple Versions of Microsoft Office

HTH
RDH

Not exactly sure what you are doing or wanting. But you would not change the Record Source for the Report, you would include the query with the needed results in the current Recordset that the Report in bound to.

RDH

If I understand your question ……. the “Random Read” in the post title makes me wonder if I do.

You can set criteria in a Query to select a specific record. You can also use the “Where” parameter of the DoCmd.OpenForm and DoCmd.OpenReport methods to specify criteria.

HTH
RDH

What are you attempting to calculate? You may have to build a seperate query to calculate the results needed.

RDH