Search results for query: *

I am having problems getting the treeview control to work reliably. The nodes are built dynamically. I'm building the top level nodes initially as the page loads. I'm then using the _TreeNodePopulate() event to add new child nodes as I click on a parent. THis is all working fine. As I add a new...

Leanne, You can get hold of the ID for the newly inserted record by running a select statement like "SELECT RecID FROM inserted" where RecID is the name of the auto-number field you're interested in. To make things simple you could assign this value to a variable and use this variable in your...

actionbasti, You don't want to close the form that holds the list box until you've at least set the gCurrentProjectID variable, as this needs to reference the list box to get it's value. This is where the error is voming from. Try moving the DoCmd.Close line to the bottom of the routine. To...

The ADP is usually shipped as disconnected - we have a routine that we run to drop the database connection. Otherwise, the ADP remembers it's last good connection (CurrentProject.BaseConnectionString) and tries to reestablish this as it starts. We use a text file that stores the customer's...

I have an Access ADP that has been developed in Access 2000. All works fine, but if I convert it to Access XP or 2003 then it gets corrupt if it's moved and cannot establish it's previous connection when restarting. Have gone through the usual Decompile, compile, compact and repair. Seems to...

Thanks, but I'm not sure what you're referring to... This is an Access Data Project (.adp) that uses an SQL Server database rather than a Jet database. There is no Queries tab, but in the list of objects in the database window you see the Tables, Views and Stored Procedures from SQL Server (as...

I'm having problems running reports in an Access 2000 ADP where the report's recordsource is a parameterized stored procedure (SQL 7/2000). The parameters are being passed via the report's Input Parameters property, and are derived from a dialog box. This was working fine until the database...

The subform is actually a control on the parent form. To refer to a control on the subform itself, you need to use the Form propery of the subform, e.g. [Forms]![ClientForm]![SUBFORM].Form.[Sale ID] This should work.

I'm having problems running reports in an Access 2000 ADP where the report's recordsource is a parameterized stored procedure (SQL 7/2000). The parameters are being passed via the report's Input Parameters property, and are derived from a dialog box. This was working fine until the database...