Search results

Hi Tom, I have seen this issue as well. Where, for instance, and DAO Record Set was not closed and would orphan the DB in an open state. That is not the case here. I did check for that. I compacted and repaired both DB's, then re-opened from a clean slate holding down the shift key to bypass...

Hi Doc, I believe this is a technical issue not related to the conventional or typical causes for this error. I have been working like this for a long time, and only recently ran into the issue. Nothing has changed except for updates to Windows and Office.

I have full control of all Files and Folders. I am the Owner and Administrator of all my machines and not attached to any Domain Controller. I do have UAC enabled but I do not get the UAC permission window when I install programs etc. Interestingly enough, I looked at my Local Folder...

The database has been placed in a state by a user on a machine that prevents it from being opened or locked (Error 3734) I have a client that likes to make changes to his version of the application. I maintain the developer master copy and so I need to merge his changes, etc., with my copy and...

A CSV File is technically a Text File. Once it is opened in Excel, the Long Numbers are destroyed and converted to exponentials. I always stress to clients to NEVER open a CSV file in excel before it is imported. If it is converted, you can use VBA to first open it in Excel and TRIM() the...

Yes, I corrected myself in my most recent comment just two responses above yours, once I read about the security requirements. I, like you, would use as much of the built-in objects as possible. In my corrected statement, I mentioned using the ObjectID of the Table rather than the name, in the...

You can build off of the existing Access information that is already built-in. Why build it again! You can create an INSERT Query based on the MSysObject and be done with it. You can join your Obejct Table to the MSysObject Table to remove Objects that you have already inserted into you table...

Why is it necessary to do this? There is already a hidden table in Access that already maintains this information. What you are doing is redundant and a waste of precious space in the database. Unless you are doing this for educational purposes and training exercises working with Recordsets, I...

There is no need to reopen the form when the Record is saved. In the underlying record source to the Form, simply filter out those records that are in use. When the User on other FE's click the save but, simply requery the form, or apply a new filter. A lot of resources are wasted to close and...

Hmm... CTL+A then CTL+- ... this catastrophic as it will delete all records. Also, selecting individual records from the record selectors on the left then clicking right mouse will also permit record deletion. No programming required to delete records.

He may have thrown in the towel. I wonder how many folks have their hands on the data? But one thing is evident, there is no control over the data. Maybe he discovered the issue and it is him and is a little embarrassed. I think we have all been there, but we learn from our mistakes and move on.

I rely on SQL IDENTITY values and have never had an issue. Access AUTO NUMBER columns on the other hand do have a history of not keeping track of the seed value but I have not had that issue in quite some time. The issue usually occurred while compacting and repairing in older version...

That is an encrypted email. You will need to get an email decryption tool.

Why not just connect or link to your inbox in Access? If your email is in Outlook you can connect to Outlook as an access table, then you can import the contents from there. The only caveat about this solution is in a multi-user environment because only you can see your inbox and it would error...

Why not just set the Visible Property of the Controls to True or False. I only use bring to front of send back functions in design mode. And now, with the new stacking and tabular features and anchoring, new since the 2007 version anyway, I never use them. In one of my lastest apps, where it...

Please see my final last comment.

What a morning! Here are my notes from this morning. It was painful, but it is solved. I think the conclusion is that there must have been some corruption associated with the original Screen, and maybe one of the Sub forms in the Navigation Control (NC). I did not work with any of the sub...

I use the same methodology in all of my applications. I have apps connected to Azure SQL DB with various DTU levels, as well as AWS, SQL Server over the Internet running on Dell PowerEdge Servers behind a variety of VPN's and have never run into this issue before. I did not create this...

I altered the Dashboard to have a single tab in the Navigation Control. I removed all combo boxes on the subform (x3) just to render data. I also limited the data to 10 records on the SQL Source Table. The behavior is just the same.

I will add that the Row Source is a Query, not a SELECT Statement. The Recordset Type Property is set to Snapshot. The Combo Box is Limited to List.