Search results for query: *

Thanks GriffMG for pursuing this. I certainly am confused but I don't think in the way you are suggesting. At this point the app is in single-user mode so the "someone else has it open" aspect doesn't apply. Plus, as I said above, before issuing the Set Exclusive and Pack, I Close and Set to...

Thanks Mike for the "forum knowledge." However, the Pack issue is still unresolved. As I said above: I have searched throughout the program and in every case where I open conn3 and its recorset I first close the recordset and set it to Nothing.

Mike, pardon my lack of "forum knowledge" -- how do I close the threads in the other forums and reference this forum?

I have done some experimentation which seems to disprove the claim that you can't gain exclusive access on a connection if another different connection is open. To "purify" the situation I moved the Pack code to the very beginning of program execution and did the following: -- Established and...

I received the following response in another forum: So, the situation seems to be related to gaining exclusive access. Before issuing the Pack command I do SET EXCLUSIVE ON for the connection on which I want to do the Pack. What I don't understand, and what seems to be illogical, is that...

I spoke too soon about a resolution. The "midstream in the program" Pack that worked (or I thought worked) doesn't work - I get the "Can't Open File" error. However, if I Close and Set to Nothing ALL recordsets and connections, the Pack does work. (Of course, I then need to reopen...

I've done what I should have done before posting - testing! The testing shows that the explanations in my origianl post are correct, and also that the Deleted= setting DOES affect RecordCount. (By the way, before anyone wonders, I am using a client-side cursor on the recordset.)

Can someone please tell me if I'm correct or incorrect with repect to Deleted=Yes/No in a Connection String: Deleted=Yes: Deleted records are ignored. Same effect as command SET DELETED ON Deleted=No: Can access all records. Same effect as command SET DELETED OFF Plus, a question: what's...

RESOLVED! There is a recordset associated with the file (rs3). Closing the recordset (rs3.Close) was not sufficient to prevent the "Can't Open File" error. However, when I added rs3.ActiveConnection = Nothing the error went away and the Pack succeeded.

Mike, thanks for your input. There is only one user and the .HST table is not open on another connection. In fact, as part of the testing on this situation I closed conn3, set it to Nothing and then reopened it with a new connection string. Couls this situation have anything to do with the...

VB6 app using the VFPOLEDB Driver to work with free tables (.DBF files). Three such tables, each opened on its own Connection when the app is run and remain open. The following code works on one of the Connections: conn1.Execute ("USE IN SELECT([GHM_V70])") conn1.Execute ("PACK GHM_V70") In...

Resolved and my apologies. The problem was not the P&DW. It was related to a format and field name conversion of the original .DBF file to the file used by the VB app.

I should add that I can successfully run the copiled program (.EXE) from the folder in which VB is installed. What doesn't run successfully is the .EXE generated by the VB Package and Deployment Wizard -- that is, the program as installed from CD with the setup program created by the Wizard.

Mike, good to hear from you again. If you will recall, use of the direct Update command was the result of a long thread awhile back. The following is a truncated version of the code generated by the UPDATE command. There are 87 fields so the code below shows just the first few fields (the...

VB6 application named GHM using the VFPOLEDB Provider with a dBase database file named GHM_V70.DBF. conn1 is Connection String; rs1 is Recordset; PA() is an array of field values. There are 87 fields in each record. The following code for record updates (used versus rs1.Update) works...

I should have added to my last post a reference to a previous post that states that Microsoft's "solution" for the Vista full-screen situation is to install an XP Video Driver. Of course, that negates some Vista features, e.g. Aero.

It's not a problem in XP with some "juggling.

The font size is only one part of the problem. The full-screen situation (that is, lack of it) is the other part. I assume that changing the font aize does not change the size of the "shrunken window." Therefore, are you not left with a scrollable window instead of a desirable full-screen...

fbizzell, what's need is to use a Connection with a Driver that supports .DBF files. There are some dBase drivers that I had trouble with for various reasons. I ended up using a Visual FoxPro driver, of which there are two to choose from: ODBC and OLE. The OLE driver (vfpoledb) is preferred...

Thanks Lyndon. What I'm looking for are industry-wide numbers for the purpose of informing Microsoft of how many applications they have "left in the dust" by eliminating full-screen capability in Vista for applications like Clipper.