Search results for query: *

Try using the ON CHANGE instead of AFTER UPDATE

1. All yes no items should be tied to a query that produces yes (not no) 2. Take the query defined above and design a report listing the items vertically 3. Make the report a sub report of your main report and it will always show ony the yes answers reguardless if they are different for each record.

If the result is in the query as you stated, then you will be able to add it to a report, unless your report is not tied to the query. Do you know what your report's control source is?

There is a setting on the SQL server for how long it waits before it times out. You can test this by running a short query that produces a small amount of results from Access. If you get the same results in SQL as well then expand the query to grab more records or make the query more complex...

If you use the menu File, Get External Data, Import and tell it the import file is Delimited, then you can also tell it that it is delimited by "\" and the result of the imported file will be what you want. You can create a macro of the above description in case you need to import this file on...

Use the Send Object: DoCmd.SendObject acSendTable, "Employees", acFormatXLS, _ "Nancy Davolio; Andrew Fuller", "Joan Weber", , _ "Current Spreadsheet of Employees", , False

It sounds like you need to have your combo box control source be a query that lists all of the tickets.

Actions should not be turned off through options because then they are permanently off for all access apps. What should be done is they should be truned off during the running of the query and then turned back on after the query is run. To accomplish this, build a Macro and tell it to Set...

I would go with the transfer spreadsheet (all of sheet) followed by a "make a table query" that chooses the correct columns.

Yes, From the Front End, use FILE, GET EXTERNAL DATA, LINK link to the backend on the server Done

There is an APPEND Query that would add the record to a table instead of erasing the old table.

Set the forms default view in properties to continuous

By the way, Is this Macola you are attaching to?

Most of the time ODBC are not very efficient for queries. I have been quite successful with this: 1.Import your data from the ODBC Pervasive data into your access app using a "make a table query" 2.Run your process against this table Most of the time speed is no longer a problem...

Assuming your form is capturing data and sending it to a table, 1. Design a new query that has criteria set for only checked boxes for that person on the form. 2. Design a report to print your new query 3. Add a button to your form that prints the report I hope this helps.

In general, What do I have to do to move the email address data from the Customer table to the order header table during order entry when a customer is selected. Just general concept is needed.

2 questions: What version are you currently running? Has anyone had any issues with installation of 7.6.200? Any input would be appreciated.

Thank you all for this helpful information. I asked for the Pros and cons and now I will have to weigh your input on both sides. As you can imagine we are HIGHLY interested in migrating to SQL for the flexibility of making a nicer system for the end users.

Also you could set the Unique Values option in PROPERTIES of the query.

If you use the Database wizard in frontpage to design your forms, you will find that when you wish to make changes that MS has coded the forms so changes are difficult. I suggest Peter Nortons book on VB6 and reviewing the ASP/vbscript portion for connecting to database. Very helpful and you...