I created an application using MS Access 2007 that utilizes Date pickers (among other functionalities). I then saved it as Access 2003 db, but I was reported that date pickers aren't working.
Now, I'm changing other issues I found there, but I read somewhere (google search) that MS Access doesn't support Date pickers, and that one must install something additionally in order to support date pickers. If this isn't an option, do I have any other way of enabling date pickers?
Thank you
Another approach is to use Stephen Lebans' date picker. I've used it and it works fine, though it is somewhat old-fashioned-looking.
You need to distribute the date picker control with the .mdb file
Related
I am currently using Microsoft Date and Time Picker Control on my Excel file and it works fine on my computer. But when I send it to someone, it says they're missing the file.
My question is whether it is possible to install it for the user
automatically so it does not say the control is missing from their
computer?
This is for a school project that maximizes the user experience, therefore I would need it to be simple and easy to setup.
I have a simple VB6 application where I input information and store it on SQL SERVER. I went ahead and linked Access 2007 and SQL Server so that all my tables are in Access for report generating purposes. I created a mock report, and was able to generate a report for all users from the sql Table (from Visual basic) Now my question is this, on the report form in the VB application, I have a combobox that's being populated with Client Names from the sql server. What I need to do is allow the user to choose a name from the combobox and click PRINT and allow them to only generate the report for that one user. The names in the combobox have ID's assigned to them. I'm having a hard time coming up with a way to edit the query in access (where id=17) from VB to allow the report to be only generated for one user. Thanks for any and all help!
Dont you think that sending a query from VB6 to Access would be a better way instead of modifying the queries in Access.
Hope I understood your question correctly.
Having issues getting the Format String applied. Running SSDT in VS2013 and deploying to SQL Server 2014.
Settings
Result
Excel also doesn't display the selected format. Is there anything I am missing?
Answer found on technet.
This is because the new cube browser control used in SSDT (unlike the old cube browser used for earlier versions of BIDS/SSAS) does not display the formatted value, it just displays the raw, unformatted value only.
Testing in Excel reveiled format strings being applied.
Source:
http://social.technet.microsoft.com/Forums/en-US/171fa5b0-014b-4a64-a590-9c3d2392b528/ssas-2012-measure-formatting?forum=sqlanalysisservices
The FormatString setting can be viewed properly when you export your SSDT cube browser to Microsoft Excel. The older BIDS (SQL 2008) used to display properly such values, but this feature got lost in newer versions (the latter only display the DataType values without any formatting mask.)
I have run into an error with an Access Database created in MS-Access 2003. It's known the Calendar Control was deprecated in Access 2010 but unfortunately we need to keep using it. As a temp fix (until we can change to the date picker) we restored the MSCAL.OCX file on all 2010 users.
The issue:
We have a form to print schedules from a date range (using the calendar control). There is some VBA code to check to dates etc to make sure the range is accurate etc.
Everything works fine in 2003 but in 2010 the dates get selected fine on the form, is passed to the report (a print preview) fine as it displays in the footer BUT the query ignores the date range and prints ALL records (not just the records in the date range).
Is there any way I can step into Print Preview button when clicked to see what's being passed?
Any other ideas?
The issue with the filter not being applied to the report is a known Microsoft issue with certain set ups of Windows 7 and Access 2010. The hotfix found here: http://support.microsoft.com/kb/2596496 solved my problem.
I run Windows 7 64 bit and Office 2010 32 bit, when downloading the hotfix I selected the "x86" platform as that's the 32 bit. If you are using Office 2010 64 bit you should download the "x64" platform.
To find out your office version, open any office product, click File Tab, click Help and it will be on the right under "About Microsoft ".
The only way you can really do that is if your report/query is running some VBA code and put a Stop on the the VBA.
If your query is referencing the fields directly (IMNSHO a bad practice, but I'll work with what we've got) you could change them so they instead reference a VBA function that returns the results of those fields instead. Then you know what it is getting for sure.
There is one more trick that surely worked out for me as a solution, before I came across the accepted answer about hotfix on this thread. Also, because, the hotfix link leads to a valid thread, but there are not downloadable files.
The workaround:
Make a copy of the report file. Use that name in VBA under DoCmd call. Strange how it works, though. Such is the nature of bugs, I guess.
I have a SharePoint calendar which users can connect to and view/edit in Outlook. I want to be able to create a workflow that is fired when an item is changed or updated and then use an If statement to determine whether the change was made in Outlook or via the user's browser. Is this even possible? I cannot use a code based solution (much as I would like to) as I do not have access to use one.
Having scoured the net, it would appear not. The only way that I have used before, but it is clunky, is to create a field that can only be edited in SharePoint and an identical table that holds the previous version. The workflow can detect if the SharePoint only field has changed in relation to previous value held in the other table, and use this to direct to SharePoint only or Outlook only code as required.