Feedback by UserVoice

Mark Burns

My feedback

  1. 39 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Access (Desktop Application)  ·  Flag idea as inappropriate…  ·  Admin →
    Mark Burns commented  · 

    Further, if there is a problem with the default/installed printer driver, Access should automatically revert/default to "standard"/print-to-file defaults, rather than get hung up or fail to render screens or reports at all. Allow us to select the default printing data, like HCL , HTML, or a PostScript rendering for the default settings as a group of Access Option settings.

  2. 15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Access (Desktop Application)  ·  Flag idea as inappropriate…  ·  Admin →
    Mark Burns commented  · 

    I'm guessing they are asking to replace Jet/Ace engine entirely with SQL Server's Local File store...or something along those lines (or, perhaps make Ace read/write into/with those SQL Server Local File Store databases - which have up to 10GB size limit iirc).

  3. 45 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Access (Desktop Application)  ·  Flag idea as inappropriate…  ·  Admin →
    Mark Burns commented  · 

    I understand the difficulty of this request as there is a tight relationship between the SQL view and the Query Designer views. I think it would be acceptable to allow the designer to obliterate the formatted SQL, so long as warnings were displayed before the changes were committed that will erase the formatted sql (and comments). Multiple statements could be handled in the designer simply by adding a vertical scrollbar to the right of the designer window (to scroll the multiple SQL statements). If the designer were to pop up a "Warning the SQL is in a formatted state, making changes in the designer will remove all SQL formatting." would be sufficient to allow people to decide what to do and how, or not. If you really wanted to go the extra mile, allow a special comment or something to bar the query editor from altering a formatted SQL statement. That way WE could control what things the query designed was allowed to "mess up" or not.

    Mark Burns shared this idea  · 
  4. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Access (Desktop Application)  ·  Flag idea as inappropriate…  ·  Admin →
    Mark Burns supported this idea  · 
    Mark Burns commented  · 

    Instead of a new function, add an optional parameter to NOW() for the desired timezone - and you can make the Current system TZ the default. This would permit all the existing now() calls to finction as-is, and allow the addition of parameters for timezones or UTC/Zulu or whatever.

  5. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Access (Desktop Application)  ·  Flag idea as inappropriate…  ·  Admin →
    Mark Burns supported this idea  · 
1 3 Next →

Feedback and Knowledge Base