DWUTKA at marlow.com
DWUTKA at marlow.com
Wed Oct 13 09:53:49 CDT 2004
Been having too much fun off list. Just getting over a cold right now, so my head is still spinning a bit. Drew -----Original Message----- From: Colby, John [mailto:JColby at dispec.com] Sent: Wednesday, October 13, 2004 9:23 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Recordset to a Continuous Form I was wondering when you would check in! ;-) John W. Colby The DIS Database Guy -----Original Message----- From: DWUTKA at marlow.com [mailto:DWUTKA at marlow.com] Sent: Wednesday, October 13, 2004 10:07 AM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Recordset to a Continuous Form Ah, the ol' 'Doing it just because you want to know you can do it!' philosophy. Welcome to my domain! <grin> Here's a few pointers on what you are trying to do. Number one, no, you can't. You can't 'trick' Access into using a continuous form, with unbound data. If you create a recordset, and set the form's Recordset to your recordset, you still have a bound form. The 'continuous form' feature of the form, is similar to the navigation buttons. They only work while Access is in control of the data the form represents. (bound). You can, however, roll your own unbound version of a continuous form. What is a continuous form? It's just a form that displays more then one record at a time. To replicate that in an unbound manner, you simply have to make 'copies' of the controls. This is somewhat of a pain, since Access doesn't really allow for control arrays (like VB does), so you have to create the controls you need at design time, and hide the ones you aren't using. Scrolling through the records is simply a matter of keeping track of your 'pointer' record. ie, if you have 6 'rows' of controls, to display a record (one record per row), and you have 12 records to display, at the beginning, record 1 will be in the first row (2 in the 2nd, etc...). Moving down one, now record 2 will be in the first row, and so on. I have done this before, but didn't scroll like that, I put in left/right buttons that let you jump to the next 'set' of records (moving right would put the 7th record in row 1). Why in the world would you want to do this for practical purposes? Well, the time I built my own, it was because I needed to create a dynamic combobox, that didn't work right in an bound form. I needed the combo box to display only the vendors available to buy a particular product from. In a single form, that was fine, but when I went with a continuous form, the combobox didn't 'act' seperately, changing one changed them all (because that's how continuous forms work, it's not really a control array...). With an unbound solution, I was able to set each combo box individually. It took another hour to two to build the form that way, but it accomplished the goal, and quite frankly was just as functional as a bound form. (for what I needed to use it for...) Hope this helps a little in your quest for 'Doing it just because you want to know you can do it!'! <Grin> Drew -----Original Message----- From: ACTEBS [mailto:actebs at actebs.com.au] Sent: Tuesday, October 12, 2004 10:48 AM To: access group Subject: RE: [AccessD] Recordset to a Continuous Form **I originally sent this exclusively to Joe for some reason. I clicked reply without checking the "To" field. Sorry Joe...** Joe/Charlotte, I'm screwing around trying to teach myself some new tricks and am creating a totally unbound app using A2K. I know, I know, everyone is saying, well why not use VB, but that's not the point of this exercise. So basically, I have an FE that basically opens up recordsets as needed from the BE. Problem is I can't figure out how to populate a continuous form which is one of the really cool features access has over other development environments. List boxes and combos are fine as I create a string and populate like a Value List. So any ideas? Vlad -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Wednesday, 13 October 2004 1:21 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Recordset to a Continuous Form There's not really any such thing as a continuous *unbound* form. The only thing that makes it a continuous form is the bound recordset. You can display a recordset in a grid control, but it won't behave the same as a continuous form. Perhaps if you explain what you're trying to actually accomplish, someone can help. Charlotte Foust -----Original Message----- From: ACTEBS [mailto:actebs at actebs.com.au] Sent: Monday, October 11, 2004 7:17 PM To: access group Subject: [AccessD] Recordset to a Continuous Form Hi people, Does anyone know of a method to display a DAO recordset within a A2K continuous unbound form? Also, is it possible to edit the recordset and save once changes are made? Any help much appreciated... Vlad -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com