Search results

I've never noticed a performance hit after compiling it, it should work the same as before in regards to references. Once compiled you are no longer allowed to make changes to the code or form design, so make sure you keep a copy of the original version.

If you don't want users to see code then compile it to an MDE/ACCDE and they won't be able to enter design mode any more.

You really need to look at software for version controlling, since each keystroke is a technically a change to the code, there would be hundreds to thousands of changes each time the programmer touched the code. With some of the previously mentioned version / source code management software the...

Well you can append all the data from the production copy to your local copy then push your copy and overwrite the one on sharepoint. Aside from that there really isn't a great way to do version control and preserve data. Ideally a back end shouldn't be changed once it goes to production, I...

I believe your interpretation is correct, I think Bob Larson had a post about Access 2013 in here, and his experience with it was not a great one. They are really pushing it to sharepoint/web development.

I would say it is not advisable, though I'm sure it is possible. I think this type of activity is akin to creating the tables in the first place, it is more of a one time setup, if you are needing to create/delete/re-create table relationships then perhaps the database design needs to be...

I guess I missed the part where you said you were using the wizard to create code. When creating a form I add a control, then go to the event handler, add the event and it pops up a choice for Code Builder, then I'm in the VBA window and can code to my hearts content.

I have Access 2010 at work and I am able to directly create VBA modules, and code just as before, I'm not sure what issue you are referring to.

My first thought here is that these lines KillProcess "acrobat" psFillBrowserWithDefaultPDF Kill (sSelectedFile) are happening too quickly, try putting a sleep or some type of wait after the KillProcess, 1 second should be enough, the thought is that the process hasn't terminated yet and...

Can it be done, yes. Should it be done, sure why not. If I needed to do what your are trying I would use the Open and Close file command along with a recordset object and export the CSV myself. Exporting the header and trailer at the appropriate time. If you don't want to write your own CSV...

In access / vba dates need to be encapsulated with ##, try DoCmd.RunSQL ("Update tblTmpSupplierOrderAllDetails set PurchaseOrderDate =#" & Format(Me.dteInvoiceDate, "dd/mm/yyyy") & "#")

spikepl is correct, you can search/extract whatever you put into the database. If you want to store the actual PDF files in the database as objects in the table I would caution against that unless they are very small files, otherwise you will run out of space quickly.

I guess I misunderstood, if you don't care which forms are open, and you only want to know if there are forms open use Application.Forms.Count, it will return the count of open forms, so if the count = zero, no forms are open. You can always leave off the = True part when the function is a...

When you say searching through a PDF do you mean you are creating database fields that contain data about the PDF, or you actually want Access to search through the contents of the PDF file?

I would write a function in a public module, then pass the form name you are looking for. Public function IsFormOpen(frmName as string) as boolean if syscmd(acSysCmdGetObjectState,acForm,frmName) = 1 then IsFormOpen=true end if end function

I don't know why, but try wrapping the Counter with a cstr() .Fields("Counter").Value = Cstr(Counter)

The line in red above strikes me as the possible culprit, in VBA an Integer is a 2 byte number, in vb.net a long is a 4 byte number. Try changing it to dbLong

Is this VB.NET or VBA, where is this code running from? Can we see your variable declarations, what datatype is rs, what type is Counter?

Pseudo code in this case isn't all that helpful. If you can please post the actual VBA routine that is running, what you wrote in your pseudo code may not be what was actually coded.

Wow, this is a disturbing trend by MS. I am disappointed in Windows 8, and now that I see Access 2013 it is continuing the trend of mobile/web support. While that is perhaps the future dominant technology, business is always slow to adopt, and quite frankly I can't see how crunching accounting...