Search results

I think there's some odd stuff in this thread. 1. while most everybody today uses TCP/IP networking, at the time Access was created, TCP/IP networking in environments where Access was being used would have been relatively rare. The most common networking protocols back then would have been...

I would think the reader should be able to figure it out, but in my opinion the correct variable declarations would be: Dim Msg As String Dim Style As VbMsgBoxStyle ' alternative is Long Dim Title As String Dim Response As VbMsgBoxResult ' alternative is Integer

This is terrible coding practice: Dim Msg, Style, Title, Response It's essentially declaring all variables as variants. Data types should always be declared as the most restrictive type possible. Why does it matter? Well, recently Symantec has been having its anti-virus updates fail, starting...

Is there anything in ACCDB that you use that is not supported in MDB? If so, is it something that is convertible (like multi-value fields)? It might be substantially easier to convert to MDB format than to try to integrate with Sharepoint. Of course, "ease" is in the eye of the beholder, and...

I don't think Jet replication is a valid response to the question as asked, but maybe there's more information that was omitted that would make it relevant. Jet Replication Wiki http://dfenton.com/DFA/Replication/

This is easy if two assumptions are correct: 1. your back end is MDB format and not ACCDB. 2. you are going to synch the laptop with the file server via a wired LAN (not over the Internet and not over WiFi). If #1 is not true, then there is no built-in synchronization -- the only synching...

Perhaps you would get better assistance in a forum devoted to MySQL, instead of one that's about Access?

You should check the MSysReplicas table to see exactly how many replicas there are with the path/filename/UNC path that you're trying to delete. In certain circumstances I've never figured out, it takes as many attempted synchs to completely delete a replica from the list as there are records...

Microsoft does not issue patches/hotfixes for individual databases, only for its own applications, in this case MS Access. So, by definition, a patch/hotfix for Access from Microsoft is going to change the way Access works with all databases.

Yes, replicating a table changes the default on an Autonumber from increment to random. Replication is perfectly available in A2007 as long as you use the MDB format. It is only the ACCDB format that has been crippled by removing this functionality. In A2007, Sharepoint was promoted as a...

The quotes are out of date, period, end of statement. Luke Chung has tons of articles out there that have information in them that dates back to A97 and has not been updated (many of them on MS's website). Just because it's stated on the web indeed does not make it true. Access defaults to...

I lived through it, changing the setting in A2000 and not needing to do so in A2002 and A2003. If you don't believe that, well, there's nothing I can do about it. I don't understand why you feel the need to make an issue of it.

Option Explicit is on by default in Access *after* A2000. All other Office programs default to having it off and always have. I don't have a pristine Access installation to check this on, nor do I have the time or interest in re-installing Access to check. The articles you cite are simply out...

I'm sorry, but this is pure gibberish to me. I haven't a clue what you're talking about. This is an Access forum, so the context is not one that applies to anyone but Access programmers (or users of Access who create code with the wizards and so forth). Since Access is a database application...

This is not really any different from using DoCmd.RunSQL, as you have to call DoCmd.OpenQuery, and if you don't want to bother your users with the confirmation messages, you have to turn off SetWarnings and then turn it back on. So, the exact same problems adduced for the other solutions are...

Better: CurrentDb.Execute "DELETE * FROM TableName WHERE FieldName < DateAdd('d', -90, Date())", dbFailOnError And then you'd need to add an error handler. Or you could use my SQLRun() function, which does all this for you...

Well, if you need to store a value that exceeds the capabilities of a certain data type, you have to choose another data type. You wouldn't choose currency or double to store whole-number values, not just because they take up more space, but because they could allow non-whole numbers. It's a...

The solution has already been provided. Change this: Public Const SCARD_PROTOCOL_RAW As Integer = &H10000 ...to this: Public Const SCARD_PROTOCOL_RAW As Long = &H10000 That will fix the problem. You don't need to worry about trying to reference a .NET library, because the variable...

You use integer data type if your data is within the limits of the integer data type. It has nothing to do with storage efficiency -- it's entirely a matter of strongly typing your variables so that you can't store a nonsensical number in a variable.

It would seem that VB.NET uses "integer" data type the same way SQL Server uses it, i.e., a SQL Server integer field is the same as a Jet/ACE Long Integer. In this case, your constant is too large to be stored in a VBA Integer variable, which is limited to values from 32,768 to 32,767. The Hex...