Search results

Focusing on the VBA part - yes it is very possible to write code that are compatible across both Access versions and for both n-bits platform. You'd use conditional compilation. An example: #If VBA7 Then Private Declare PtrSafe Function ShellExecute Lib "shell32.dll" _ Alias "ShellExecuteA" (...

If the text files are essentially a list of binary sequence of a certain size, then I'd just create a table with BINARY(N) with N being the size of the binary and insert into it. Recall that Byte() and String data types can be used for binary manipulations

Yeah, that's one more option. Last time I fiddled with FMP, though, I wasn't really impressed - it felt more like an electronic rolodex than a platform to build a line-of-business application on. I know in recent versions, FMP has been doing more developer-centric stuff but also expect you to...

I believe Galaxiom is misinformed - there was never ever an Mac client for Access since Access 1.0. I also think he missed out on the crucial point that Office 2011 re-introduced VBA. Back prior to Office 2008 release, they announced, "No VBA" and I thought "Oh well. That's it." I was wrong -...

How exactly did you get it to work without the unreachable Resume? When you ctrl+break, you are taken to the line right after the MsgBox and if it's in an error handler, you'd need to use the Resume to return you to the actual line that failed.

Have you ever stepped through code before? This is essentially what is being done when using the unreachable Resume trick.

Ding dong, we have a winner! The expression "(Table.Field Mod x \ y) = 1" is definitely not sargable and therefore looping would be just as fast. Come to think of it, even if we have & operator available to us, it'd still not be sargable unless we also create functional indexes. I'd think...

Because SQL's AND operator is a logical operator, not a bitwise operator. The equivalent in VBA would be more like: "CBool(x) And CBool(y)". When you evaluate 8 and 4 both as a Boolean values, they turn into a True value and therefore it's "True And True", giving you a True. Galaxiom is...

This is not the exact same thing but in my humble opinion more than good enough: On Error GoTo ErrHandler ... ExitProc: Exit <procedure> ErrHandler: MsgBox Err.Number & ", " & Err.Description Resume ExitProc Resume When I get a messagebox with an error, I just need to use Ctrl +...

Gemma - SQL's "AND" operator is logical and there's no bitwise operator in SQL. It may work in VBA since VBA's "And" operator is bitwise and by extension could be also used as logical operation with caveats. In SQL, though a "AND" would only give you "True" (aka -1) for the expression "128 AND...

It's probably because you're trying to use an operator for bitwise comparison when it in fact has nothing to do with it. It's a happy accident that it works for some numbers in very much same way that 2 + 2 and 2 * 2 happens to have same answer, 4 but no other numbers that's not zero or one has...

Afraid the answer is going to be "it depends." Don't you hate that? :) But the relevant factor you need to think about is this: 1) Do you need it to be updatable? This is especially important for binding a form. Reports can be based on a non-updatable data source, and therefore you certainly...

The answer is going to be possibly no, not at first. See, so much depends on how well-designed your applications are. To give an example - if you have a form where you allow your users to filter using say, Access' built-in Filter-By-Form functionality and it performs decently with a Access...

If it doesn't exist, it should return error 429. You can then use error handling to trap for that error and do nothing. Note for benefit of posterity: Both "CreateObject" and "GetObject' will return error 429 but it actually means different thing - GetObject's 429 = "We couldn't find a...

Yes, you do need to install MySQL ODBC driver on their PCs. That's the only thing they need besides Access to be able to connect.

Actually, I like Mr. B's idea much better. I'm sure you should be able to do this: SELECT * INTO NameOfNewTable FROM SharePointList WHERE 1=0;

I'd think the simplest thing to do this is to do something like this: Dim ltdf AS DAO.TableDef 'Local copy Dim stdf DAO.TableDef 'SharePoint list Dim lfld As DAO.Field Dim sfld As DAO.Field Set stdf = CurrentDb.TableDefs("<name of list>") Set ltdf = CurrentDb.CreateTableDef With ldf .Name =...

I totally do love the idea of being to wrap the form editing in a transaction, but the whole idea was to be able to save oneself from having to code in the checks & bulk operations & whatnots and using Rollback/Commit & associated errors to manage data entry. Long ago, when I tinkered with it, I...

Okay, played with both LagBolt & Leigh's code to refresh my memory. Glad for that. I can confirm that Lagbolt's starting transaction before setting recordset to the form works but in Leigh's case if I move the BeginTrans before I set the form's recorsource, I get error 2074, not supported in...

Lagbolt, Haven't yet tested but few quick comments: 1) Leigh's a he, not she. :) 2) One scenario that I definitely know will not work is if you want to have a transaction span multiple recordsets - think of the form with a linked subform - years ago, I had a need to be able to control the...