Search results for query: *

Check out the References.AddFromFile method in the Visual Basic Help.

Wow, I just tried decompilation. My Front End went from 1.3MB to 488KB. My Back End went from 6.1MB to 3.4MB. Thanks foolio, for sharing this info.

Are you trying to declare a variable and name it using variables? I don't think this is allowed.

Do you have a lot of code behind the forms? If the code is still intact, I would do the following: 1. Copy all the code behind your forms into text files. 2. Delete all of the code behind the forms in your database. 3. Start a new .mdb file. 4. Import the forms and any tables from your...

I guess the problem I'm having is that I need to use Row Level Locking (Pessimistic), but say two users try to simultaneously add a row of data. This causes their computers to freeze and eventually display the message, "This record is locked by user, %WindowsLogonName% on machine...

Say I want to code some custom error handling whenever the row is locked by another user. How would I need to set the options in the application in order to turn off Access handling the record locked condition? I have the following code in the BeforeInsert event of the form where record locks...

Haha, that's where I got the connection string that's in my post.

My application uses row level record locking in a multiuser environment. Does anyone know how to check if a row is locked for editing?

You don't need to instantiate the Access application. You can use ADO to connect to the database via ODBC. Dim oConn As ADODB.Connection Dim rst As ADODB.Recordset Dim strSQL As String Set oConn = New ADODB.Connection Set rst = New ADODB.Recordset Set oConn = "Driver={Microsoft Access...

As an update, I fixed the problem by changing the CursorLocation property of the recordset from adUseServer to adUseClient.

VBAinspire, Did you ever figure out how to correct this problem? I am getting the exact same error. I wrote a function that uses the CopyFromRecordset method to transfer data from access to excel. It worked for months on end and then my boss got a new laptop. The function breaks only on his...

I was in a hurry earlier, and didn't have enough time to go into any detail about what this function does. After reading my post, I realized it didn't really offer any information conducive to troubleshooting. So here goes: I use the function to open a recordset of data from my Access...

I am getting the error in the subject line when I execute the following function. I marked the line the debugger is stopping on. Public Sub ExportToExcel(rptType As Integer, _ JobID As String, _ startdate As String, _ enddate As String) On Error Resume Next 'Turn off error...

Thanks MDXer, this solves my problem, but I don't see any way to make it not display in 24-hour time. If it's not possible, I'll just make another varchar column alongside the time value in the 12-hour format, bring it into the view, and use that as the display member for the ComboBox.

Well, I am populating it with a DataView. Maybe if anyone knows how to force a column in the dataview to format as a Short Time, that would solve my problem.

I am using a ComboBox to display time values in a DropDownList. The values get pulled from a SQL Server database. The field in the database is a datetime field and I enter the values like "6:00:00 AM" When I pull these values from the database and use them to populate the ComboBox...

I have an Access front end that gets used on multiple computers in a network. In the master file, under the Tools-->Options-->Advanced Tab, I have set the record locking scheme as follows: Default Open Mode: Shared Default Record Locking: Edited Record Open Database Using record-level locking...

I could filter the form in its own load event, but I would have to make sure that the main form is open if I'm going to filter based on the value of one of the main form's controls (and this seems impossible since the event firing order changes every third time the form is opened). However...

Thanks Jedi420, I did a bit more testing of the problem and I have figured out why it is happening, but I still can't figure out how to stop it. According to the Access 2000 documentation, the following events fire when a form first opens: Open --> Load --> Activate --> Current I got curious...

I have a main form with a subform on it. The main form has a Calendar Control on it. When the main form loads, I set its recordsource and I set the date for the calendar. I then use the calendar's date to filter records in the subform. Here is what's in the load event of the main form...