Search results

Maybe I'm missing something but I didn't see anything that would prevent you from setting subform just the same way you would have set it up with Access tables. Are your MySQL tables linked? If so, you should be able to set up subform normally - set the subform's LinkMasterField and...

No. It's still supported in all versions. Just harder to create a new ADP than in previous version (there's no longer a obvious menu option as there was in 2003 but it's still there nonetheless). I'd also not recommend creating/starting a new ADP at this point. There's really nothing new for ADP...

I think there's something else going on, because I'm very fairly sure that periods was never allowed in an Access object name. I have a strong hunch that your 2002 file is actually an ADP file and you imported the objects into an ACCDB file. An ADP file interfaces more directly with SQL Server...

I think it may also help to differniate between security in the sense of securing and protecting unauthorized access to data from "access control" which merely grants/deny you the access to interface you need to manipulate data with. As former, ULS sucked. As latter, ULS did work pretty well...

1) I usually recommend that you base your forms on a query, not table. Query allow you to control the presentation of data more than if you based on table. Forms may have some properties that allow you to work with data but my experience is that queries are more reliable and simple to use. 2)...

1. Did you base your form on a query that has a order by clause? 2. How many items do you have in the lookup? Did you create a lookup field? 3. If you mean built-in one, it's a part of the Navigation bar shown on the bottom. You may need to enable Navgiation Button = Yes in order to use the...

In *theory*, you would be able to create 2007-friendly files with 2010. In practice, however, I feel that it's far too easy to slip up and introduce 2010-only entities like Bob mentioned about themes and thus rendering the "2007" file format 2010-only. For this reason, if you develop with...

The other alternative is to move your data into a server-based RDBMS. If you don't want to pay for one, there's several free editions available (SQL Server Express Edition? MySQL? PostgreSQL?) and keep your exisitng Access application as a front-end to those servers' tables. This works well...

May I ask what is numbers of records we're talking here, and what is the underlying SQL for the recordset?

Why not retrieve the bookmark and set the recordset to that bookmark?

To see the problem, we'd need to see the SQL.

Your query doesn't have to actually produce horizonally aligned anything. What you need to focus on is summing up the income & expenses and grouping by months Something like this for a starter: SELECT Month([Date]) As Month, SUM([Income]), SUM([Expense]) FROM tblIncome LEFT JOIN tblExpenses ON...

What you are asking should definitely be possible with Access PivotTable. However, I have to confess I don't know for a fact whether you have to build similar data structure to get the same result in Excel as you would have with Access. Can you provide a bit more information on how you have...

Responded.

Seem to me that this sort of this thing would be done by doing something like this: 1) Gather all names of the functions and sub, which you seem to have already done with ProcOfLines. 2) Go through all modules and scan the procedure for any tokens that matches the list of procedure you've...

Wayne also exposes this sort of thing with his vbWatchDog product (a commerical addin).

and if the public ones are member of a COM interface as well. If you don't have an interface, then your DLL can only be late-bound. I wrote an example some years ago that discusses the requirement to enable early binding.

A possible DIY example is to set up your error handler to allow errors to bubble upward and gather the information. Example: Public Sub TryIt() On Error GoTo Error_Handler A Exit_Procedure: On Error Resume Next Exit Sub Error_Handler: Select Case Err.Number Case vbObjectError...

I would think that the purchase consideration would be basically same as a database server for a big iron software. Namely, you may find a system with fast disk subsystem better suited than one with monster processor & boatload of RAMs. I'd wager that an Access (as well as any other database...

A common mistake with IN() is to assume that it means "parse whatever I pass in the ()s" when it's actually a compile-time shortcut for longer form of: WHERE x = a OR x = b OR x = c ... Thus, IN() cannot be use in a dynamic sense. A common approach, instead is to use an ad hoc query that runs...