Search results

Hi guys, My problem is that Im getting the error from the attachment when running my code. The error probably happens because the code query didn't manage to update the field/s within the given timeout which is 60 seconds, but thats not the real issue. When I execute the exact same query...

Today I faced another issue when trying to export a report into Excel, Word or whatever uses the Access export wizard. I tried by removing again the mentioned files above but it didnt fix it. Luckily I have the same Access version 2010 and copied my files (the exporting works fine on my PC, as...

Found the solution. I did it the "Let me fix it myself" way. Link to the solution: Acc2010: You receive an error in Microsoft Access using the built-in wizards after installing Microsoft Office 2010 SP1 Link where I found the solution: Linked Table Manager says VBA project cannot be read...

Hey guys, unfortunately no luck. I did a repair but the error still occurs. I added in the attachment the second message. I cant access the linked table manager without having at least one linked table, so I cant find that out. The option is grayed out if only tables of the current database are...

The table I linked is from another fresh database I made, also completely empty. I will try the shift key later, thanks.

You misunderstood me, I didnt transfer anything to the new database. The database is completely empty without any code, just one table and its the default one access makes so I saved it.

1. Yes 2. All same as on my PC 3. I made it in Access 2007 (have to check the exact version) After the error there is another message which I forgot to screen, it states that the object Im trying to access is broken (something like that). Today when the server is free I will do a repair of the...

Im developing the .accdb at my PC which has Office 2007 and Office 2010, Im using Office Access 2007 for this .accdb. On my PC in this location C:\Program Files (x86)\Common Files\Microsoft Shared\VBA I have VBA6 and VBA7 folders In Program Files (without x86) I dont have the VBA folder...

Yup thats what I wanted. The tool above looks good but I went with the Database Documenter because I started before seeing the tool. However, good to know about it.

Hello, Is there something like a shortcut for doing this instead going through every query, form, report and code line for fixing them with the new name of the table? Thanks

I guess :) Probably the solution would be to make separate reports instead just one like now, so I dont have to set through code the control source. Now is only one report but its controls are changed on report open

Yes its dynamic. I did as you said, disabled it in the code and have put it through design view and the report/access doesnt crush until I set the control source in two of the text boxes through code. One of the text boxes is located in the custom Group on footer and the other one in its header.

It works fine until I add the Me.GroupLevel(0).ControlSource = "Something" in VBA on Report open. Then it crushes. If the query is smaller then it doesnt, or if I remove the [Pages]

Completely from scratch I didnt try, too time consuming. However, I did make a new report and was coping control by control from the old one and thats how I found the cause. The report uses Group & Sort and Im using Group on on one field and sort on another one, Im suspecting that this grouping...

Here some more details... Using only this ="Page " & [Page] the report works. However, when I add only =[Pages] or I use this ="Page " & [Page] & " of " & [Pages] the report/access crushes.

Just one page

By removing the text filed in page footer which shows the page number. Its control source being ="Page " & [Page] & " of " & [Pages] the report doesnt crush anymore...

The .mdb which contains forms, reports n queries is about 3MB, the backend .mdb with tables is about 72MB

I forgot to mention that I also tried this (found it on stackoverflow): Remove Binary Data from Form Sometimes the crashes occur in a single form or report. If it is corrupt binary data, then the crashes should be occurring on different computers, with different users. If this is the case then...

Some strange thing is happening. The report crushes on opening, but not always. As it seems only if the query which the report uses is "big". I did the debugging but it doesnt crush at any of my code lines but at the very end, when the "End Sub" is executed. This is all happening in Office...