Search results

To the best of my knowledge, nothing has changed. I'm the programmer and I've changed nothing. For example, one report which has been operating since about 1996 without revision is now generating a 2nd blank page - the only change being the version of MS Access being used and the conversion...

Sorry but not a viable answer. Many of these are reports going out the door to customers. Many others are being used by company executives. They don't want to use a magnifying glass to read their reports, and we're are dealing with dozens of reports. I'm faced with changing much of the...

I just converted a program to Access 2007/2010 format. It's a program that started in Access 95 so it is very mature. However, after the conversion, field sizes in many instances have been too small for the size of the data. Instead I have forms and reports with ##### printing instead of the...

yes, I fear that you are right. Sure wish I could determine what is going wrong.

sorry - supremely ignorant of any scroll wheel event. So used to worrying about the scroll wheel from prior experience, I wouldn't use it anyway. I would prefer to disable the computer reading the scroll wheel when in MS Access, if such a thing is possible.

sorry - did that from the Access 95 era. Each user has his/her own front end on their individual work stations. Back end on the Server or NAS device.

I remember in earlier versions of MS Access (95 & 2000), a user could corrupt a table with a memo field by using the scroll wheel of the mouse and essentially scrolling right out of the record. This is in a bound form with the cycle property set as Current Record. The problem appeared to be...

Hold On! This method seems to be causing me a problem with updating certain files. I think it is not updating transitory local files. I'm referring to tables that are created 'on the run', updated and then the data is passed to a permanent table in a different format on a networked back end...

someone sent me the following suggestion and right now it is working like a champ. I have yet to implement it across a full network but will do so later today so we'll see if it is as successful as it seems to be: http://www.fmsinc.com/MicrosoftAccess/Performance/LinkedDatabase.html go to...

Sometimes when making just a minor change in an Access 2007 or 2010 program, the system will freeze for minutes at a time - up to 5 to 10 minutes with the "Microsoft Access Not Responding" message What could be causing this problem? My FE database in this case is about 40Mb. I sometimes...

I'm afraid it was much easier to do than all the concepts passed to me. I thank you for your help. the FileCopy statement did the trick. FileCopy stSourcePath, stDestinationPath I threw in a routine to make sure the destination subdirectory was created before the FileCopy, and then executed...

I tried this approach. I had to identify a DLL to use, so I chose: C:\Windows\SysWOW64\sccrun.dll It compiles but when executed it gives me an "Path Not Found" message The statement I am using in my VBA is: fso.MoveFile C:\PDF995\OUTPUT\*.* P:\Billing\12973\44141.pdf Both paths do exist...

sorry to persist, but I'm under the gun. I am trying to copy a pdf file between 2 directories. I am using xCopy, although I'm not married to it. When I build my copy statement based upon various parameters, it looks something like this: xCopy C:\PDF995\OUTPUT\*.* P:\Billing\12973\44137.pdf...

thanks. the method works as advertised and I'm on to the next problem

I'm starting to automatically save PDF copies of certain reports in predetermined locations. I need to copy a file to a particular directory (based upon various criteria), but if the directory does not exist, I want to create the directory on the fly first. Otherwise I will just proceed...

In the distant past I've written .adp programs that linked to SQL Server 2000 and they were very nice but kinda hard to maintain from a distance. Plus, at that time SQL Server 2000 required an actual File Server, such as Windows 2000 Server or 2003 Server, which was kinda pricy and was outside...

Myrtle: no offense taken. I'll log in there and try you suggestion. thanks for the info.

Circumstance: A database shared by 2 workstations. the Back End is on a shared Network drive, the front ends reside on each workstation. I'm told that when a user is entering data on one workstation and someone signs into the program on the other workstation, bad things happen. Tonight there...

I recently had a similar problem with someone on a WIFI network who was far enough away that it went off-line with some regularity. My solution for a relatively novice programmer would be: 1) create a format identical to the BE table on the FE program with a different name. Easiest way: While...

thanks - that did the trick beautifully.