Search results

Well - I took a look at your database - the design is not what I was used to, but I think you can use the following code to achive what you want. You will need to put an Event Procedure on the on Format event of the detial section of your report and then add this code: Private Sub...

check out this site - someone with the same question - the answer is not perfect, but it might help. http://www.database-forum.com/ftopic12297.html

DoCmd.OutPutTo acOutputReport,"name of the access report", acFormatSNP, "name of the snapshot file", True

In the design view of the query in the grid section (bottom half) under the "Test Code" field in the "Criteria" row type in the following Not "TestCodeValue1" and Not "TestCodeValue2" and Not ... Of course you will have to put in real data values instead of "TestCodeValue1" and so on.

Irina - Looking at your SQL I can't see any reason you would need the events table in your query all it is doing by being there is doubling your records and causing your sum value to be to large. Why do you need that table in the query? Try the SQL: SELECT Sum(Payments.AMOUNT) AS...

Yes - Put the code in a new module. If you want to use that code you will need to be using DAO, so when you are in the module go to "Tools" on the menu bar and select "References." When the references window comes up you need to see a reference to the DAO 3.6 if you do not then your database...

-1 is a yes in an Access Database and 0 is a no. As for your other problem, Access will not let you establish referential integrity if you are joining part of a multi-part key to a single primary key. I am not really sure why Taxable would be part of any of your keys anyway, but it may need to...

I think I would try the following: In the Detail section of the form I would create a textbox with the formula: IIf([Taxable]=-1,([Item_Cost]*[Quantity])*0.0556,0) (note the change to -1 from 1) and call it say TaxableAmount. Then in the form footer put =sum([TaxableAmount]).

Where are you creating the new records? It may not be an issue with the table but with the object you are using to add the data into the table with. Maybe you are generating a blank record with that object, but it is not being saved.

Here is function you can try - This is for a DAO database and will not work for ADO: Public Function BillingDays(dteField As Date) As Integer Dim rstDates As Recordset Dim strSQL As String Dim dtePrev As Date strSQL = "SELECT date.Date " & _ "FROM [Date] " & _ "ORDER BY...

I tried that with no success. I was able to move the report prepation code to the onclick event of the button and take it off the report and that worked. Thank you for your response!

I hope someone has some ideas on this one. I am using Access XP. I have a report that I am sending directly to the printer from a button on a form. I have some code in place that updates the data for the report in the On Open event of the report (I tested every event procedure for a report...

I will try it out. It runs at night so I will not know if it works until the morning. Thanks!

Thanks for the reply. I tried the fix you suggested, but no luck I still get the same error. I am hoping that you have actually seen this problem before so that I can at least know that it is fixable. Do you (or anyone else out there) have any other ideas? Thanks,

I have written some code to export a query to excel. I am using the docmd.transfertext command. When it hits the line of code that executes the export the error "Run Time Error 3190. Too many Fields defined" comes up. The query I am trying to export has only 15 columns and I have repaired...

If you GroupBy color, GroupBy Time, Min Value. Then in a new query bring in original data and the results of the above and do join and then add the name field you should get what you want. You could create a triple join between the tables to insure that you only get the minimum records. GumbyD

They way we did it was by adding a registry entry - but we have a full profile added in when a user opens the software in Access. We added a key called "Run-Time Options" and then inside the key added a string Value called "Icon" with its value set to the icon's path. If you are not opening...

The findfirst method comes with a where clause check. In your code I would set variables to the value in List14 and combo1 (in less List14 is a multiselect list box?). Ok so here is some mock code for you: Public Function FindFirstCodeSample() Dim strBx14 As String Dim strName As String Dim...

Not sure if this is what you are asking, but if you go to tools, options if you have the "windows in taskbar" item selected then uncheck it. Is that what you were looking for?

Pat - Thanks for the reply. Yea - I checked all of the referenced files to make sure that they were exactly the same file and version. It is very odd. I have seen a lot of reference oddities with Access XP on XP Pro, but as of yet I have not been able to determine why. Since this posting...